From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net v2] i40e: fix the panic when running bpf in xdpdrv mode
Date: Wed, 14 Apr 2021 19:08:37 -0700 [thread overview]
Message-ID: <20210414190837.0000085a@intel.com> (raw)
In-Reply-To: <CAL+tcoBVhD1SfMYAFVn0HxZ3ig88pxtiLoha9d6Z+62yq8bWBA@mail.gmail.com>
Jason Xing wrote:
> On Wed, Apr 14, 2021 at 12:27 AM Jesse Brandeburg
> <jesse.brandeburg@intel.com> wrote:
> >
> > kerneljasonxing at gmail.com wrote:
> >
> > > From: Jason Xing <xingwanli@kuaishou.com>
> >
> > Hi Jason,
> >
> > Sorry, I missed this on the first time: Added intel-wired-lan,
> > please include on any future submissions for Intel drivers.
> > get-maintainers script might help here?
> >
>
> Probably I got this wrong in the last email. Did you mean that I should add
> intel-wired-lan in the title not the cc list? It seems I should put
> this together on
> the next submission like this:
>
> [Intel-wired-lan] [PATCH net v4]
Your v3 submittal was correct. My intent was to make sure
intel-wired-lan was in CC:
If Kuba or Dave wants us to take the fix in via intel-wired-lan trees,
then we can do that, or they can apply it directly. I'll ack it on the
v3.
next prev parent reply other threads:[~2021-04-15 2:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 6:57 [Intel-wired-lan] [PATCH] i40e: fix the panic when running bpf in xdpdrv mode kerneljasonxing
2021-04-12 21:52 ` Jesse Brandeburg
2021-04-13 2:17 ` Jason Xing
[not found] ` <20210413025011.1251-1-kerneljasonxing@gmail.com>
2021-04-13 16:18 ` [Intel-wired-lan] [PATCH net v2] " Jesse Brandeburg
2021-04-14 1:37 ` Jason Xing
2021-04-15 1:12 ` Jason Xing
2021-04-15 2:08 ` Jesse Brandeburg [this message]
2021-04-15 5:16 ` Jason Xing
2021-04-14 2:34 ` [Intel-wired-lan] [PATCH net v3] " kerneljasonxing
2021-04-15 2:06 ` Jesse Brandeburg
2021-04-15 10:31 ` Jesper Dangaard Brouer
2021-04-15 21:40 ` patchwork-bot+netdevbpf
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=20210414190837.0000085a@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.org \
/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