From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: anthony.l.nguyen@intel.com, David Miller <davem@davemloft.net>,
kuba@kernel.org, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
kpsingh@kernel.org, netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
bpf@vger.kernel.org, Jason Xing <xingwanli@kuaishou.com>,
Shujin Li <lishujin@kuaishou.com>,
intel-wired-lan@lists.osuosl.org
Subject: Re: [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@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.
WARNING: multiple messages have this Message-ID (diff)
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: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 6:57 [PATCH] i40e: fix the panic when running bpf in xdpdrv mode kerneljasonxing
2021-04-12 6:57 ` [Intel-wired-lan] " kerneljasonxing
2021-04-12 21:52 ` Jesse Brandeburg
2021-04-12 21:52 ` [Intel-wired-lan] " Jesse Brandeburg
2021-04-13 2:17 ` Jason Xing
2021-04-13 2:17 ` [Intel-wired-lan] " Jason Xing
2021-04-13 2:50 ` [PATCH net v2] " kerneljasonxing
2021-04-13 16:18 ` Jesse Brandeburg
2021-04-13 16:18 ` [Intel-wired-lan] " Jesse Brandeburg
2021-04-14 1:37 ` Jason Xing
2021-04-14 1:37 ` [Intel-wired-lan] " Jason Xing
2021-04-15 1:12 ` Jason Xing
2021-04-15 1:12 ` [Intel-wired-lan] " Jason Xing
2021-04-15 2:08 ` Jesse Brandeburg [this message]
2021-04-15 2:08 ` Jesse Brandeburg
2021-04-15 5:16 ` Jason Xing
2021-04-15 5:16 ` [Intel-wired-lan] " Jason Xing
2021-04-14 2:34 ` [PATCH net v3] " kerneljasonxing
2021-04-14 2:34 ` [Intel-wired-lan] " kerneljasonxing
2021-04-15 2:06 ` Jesse Brandeburg
2021-04-15 2:06 ` [Intel-wired-lan] " Jesse Brandeburg
2021-04-15 10:31 ` Jesper Dangaard Brouer
2021-04-15 10:31 ` [Intel-wired-lan] " Jesper Dangaard Brouer
2021-04-15 21:40 ` patchwork-bot+netdevbpf
2021-04-15 21:40 ` [Intel-wired-lan] " 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=andrii@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lishujin@kuaishou.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=xingwanli@kuaishou.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.