Re: [PATCH v2 0/2 net] bitfield.h cleanups
From: Nick Desaulniers
Date: Wed Aug 05 2020 - 13:54:44 EST
On Thu, Jul 30, 2020 at 3:37 PM Nick Desaulniers
> On Mon, Jul 20, 2020 at 4:35 PM David Miller <davem@xxxxxxxxxxxxx> wrote:
> > From: Nick Desaulniers <ndesaulniers@xxxxxxxxxx>
> > Date: Mon, 20 Jul 2020 12:48:38 -0700
> > > Hi David, bumping for review.
> > If it's not active in my networking patchwork you can't just bump your original
> > submission like this.
> > You have to submit your series entirely again.
> > And if it is in patchwork, such "bumping" is %100 unnecessary. It's
> > in my queue, it is not lost, and I will process it when I have the
> > time.
> > Thank you.
> Hi David,
> Sorry, I'm not familiar with your workflow. By patchwork, are you
> referring to patchwork.ozlabs.org? If so, I guess filtering on
> is your queue? I don't see my patches in the above query, but I do
> see my series here:
> but they're marked "Not Applicable". What does that mean?
I read through https://www.kernel.org/doc/html/latest/networking/netdev-FAQ.html#q-how-often-do-changes-from-these-trees-make-it-to-the-mainline-linus-tree
and noticed http://vger.kernel.org/~davem/net-next.html. Since the
merge window just opened, it sounds like I'll need to wait 2 weeks for
it to close before resending? Is that correct? Based on:
> IMPORTANT: Do not send new net-next content to netdev during the period during which net-next tree is closed.
Then based on the next section in the doc, it sounds like I was
missing which tree to put the patch in, in the subject? I believe
these patches should target net-next (not net) since they're not
addressing regressions from the most recent cycle.
Do I have all that right?