From: David Miller <davem@davemloft.net>
To: ndesaulniers@google.com
Cc: ast@kernel.org, daniel@iogearbox.net, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org,
oss-drivers@netronome.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kuba@kernel.org, elder@linaro.org
Subject: Re: [PATCH v2 0/2 net] bitfield.h cleanups
Date: Mon, 20 Jul 2020 16:34:58 -0700 (PDT) [thread overview]
Message-ID: <20200720.163458.475401930020484350.davem@davemloft.net> (raw)
In-Reply-To: <CAKwvOdkGmgdh6-4VRUGkd1KRC-PgFcGwP5vKJvO9Oj3cB_Qh6Q@mail.gmail.com>
From: Nick Desaulniers <ndesaulniers@google.com>
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.
next prev parent reply other threads:[~2020-07-20 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 23:04 [PATCH v2 0/2 net] bitfield.h cleanups Nick Desaulniers
2020-07-08 23:04 ` [PATCH v2 1/2 net] bitfield.h: don't compile-time validate _val in FIELD_FIT Nick Desaulniers
2020-07-09 1:48 ` Alex Elder
2020-07-08 23:04 ` [PATCH v2 2/2] bitfield.h: split up __BF_FIELD_CHECK macro Nick Desaulniers
2020-07-09 2:11 ` Alex Elder
2020-07-09 2:11 ` Alex Elder
2020-07-14 18:23 ` [PATCH v2 0/2 net] bitfield.h cleanups Nick Desaulniers
2020-07-20 19:48 ` Nick Desaulniers
2020-07-20 23:34 ` David Miller [this message]
2020-07-30 22:37 ` Nick Desaulniers
2020-08-05 17:44 ` Nick Desaulniers
2020-08-06 18:13 ` Jakub Kicinski
2020-08-06 18:15 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200720.163458.475401930020484350.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=elder@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).