From: "Björn Töpel" <bjorn.topel@intel.com>
To: "Paul Menzel" <pmenzel@molgen.mpg.de>,
"Björn Töpel" <bjorn.topel@gmail.com>,
ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org
Cc: kuba@kernel.org, intel-wired-lan@lists.osuosl.org,
magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH bpf-next 4/4] ixgbe, xsk: use XSK_NAPI_WEIGHT as NAPI poll budget
Date: Tue, 8 Sep 2020 13:43:22 +0200 [thread overview]
Message-ID: <9d488b02-b03f-e1ee-d4c5-12e330d567b1@intel.com> (raw)
In-Reply-To: <0b927a07-6fbb-0e5b-e791-9558c9ea8e63@molgen.mpg.de>
On 2020-09-08 13:20, Paul Menzel wrote:
[...]>> Paul, thanks for the input! The netdev/bpf trees always include the
>> cover letter in the merge commit.
>
> Yes, for pull/merge requests. But you posted them to the list, so I’d
> assume they will be applied with `git am` and not merged, or am I
> missing something. Could you please point me to a merge commit where the
> patches were posted to the list?
>
An example: A series is posted to the list [1], and when merged the
merge commit look like [2].
Thanks,
Björn
[1]
https://lore.kernel.org/bpf/20200520192103.355233-1-bjorn.topel@gmail.com/
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79917b242c3fe0d89e4752bc25ffef4574c2194b
prev parent reply other threads:[~2020-09-08 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 15:02 [PATCH bpf-next 0/4] xsk: increase NAPI budget for AF_XDP zero-copy path Björn Töpel
2020-09-07 15:02 ` [PATCH bpf-next 1/4] xsk: add XSK_NAPI_WEIGHT define Björn Töpel
2020-09-07 15:02 ` [PATCH bpf-next 2/4] i40e, xsk: use XSK_NAPI_WEIGHT as NAPI poll budget Björn Töpel
2020-09-07 15:02 ` [PATCH bpf-next 3/4] ice, " Björn Töpel
2020-09-07 15:02 ` [PATCH bpf-next 4/4] ixgbe, " Björn Töpel
2020-09-07 19:32 ` Jakub Kicinski
2020-09-08 5:38 ` Björn Töpel
2020-09-08 9:45 ` Eric Dumazet
2020-09-08 11:49 ` Björn Töpel
2020-09-08 15:12 ` Eric Dumazet
2020-09-08 10:12 ` [Intel-wired-lan] " Paul Menzel
2020-09-08 11:12 ` Björn Töpel
2020-09-08 11:20 ` Paul Menzel
2020-09-08 11:43 ` Björn Töpel [this message]
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=9d488b02-b03f-e1ee-d4c5-12e330d567b1@intel.com \
--to=bjorn.topel@intel.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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