From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Yue Haibing <yuehaibing@huawei.com>,
<przemyslaw.kitszel@intel.com>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <hawk@kernel.org>,
<john.fastabend@gmail.com>, <maciej.fijalkowski@intel.com>,
<vedang.patel@intel.com>, <jithu.joseph@intel.com>,
<andre.guedes@intel.com>, <horms@kernel.org>,
<jacob.e.keller@intel.com>, <sven.auhagen@voleatech.de>,
<alexander.h.duyck@intel.com>, <intel-wired-lan@lists.osuosl.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bpf@vger.kernel.org>
Subject: Re: [PATCH v4 net-next 0/4] Fix passing 0 to ERR_PTR in intel ether drivers
Date: Tue, 29 Oct 2024 11:37:37 -0700 [thread overview]
Message-ID: <bbcc4dcc-b599-4e47-aef7-a1f462fcd377@intel.com> (raw)
In-Reply-To: <20241029074404.282e52b5@kernel.org>
On 10/29/2024 7:44 AM, Jakub Kicinski wrote:
> On Sat, 26 Oct 2024 12:12:45 +0800 Yue Haibing wrote:
>> v4: Target to net-next
>
> Nonetheless I'm going to assume Jake / Tony will take these.
> LMK if we should apply directly.
Yes, I'll take these through IWL.
Thanks,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: alexander.h.duyck@intel.com, andre.guedes@intel.com,
john.fastabend@gmail.com, maciej.fijalkowski@intel.com,
hawk@kernel.org, daniel@iogearbox.net, jithu.joseph@intel.com,
przemyslaw.kitszel@intel.com, Yue Haibing <yuehaibing@huawei.com>,
ast@kernel.org, linux-kernel@vger.kernel.org,
edumazet@google.com, intel-wired-lan@lists.osuosl.org,
horms@kernel.org, netdev@vger.kernel.org,
jacob.e.keller@intel.com, bpf@vger.kernel.org, pabeni@redhat.com,
davem@davemloft.net, vedang.patel@intel.com
Subject: Re: [Intel-wired-lan] [PATCH v4 net-next 0/4] Fix passing 0 to ERR_PTR in intel ether drivers
Date: Tue, 29 Oct 2024 11:37:37 -0700 [thread overview]
Message-ID: <bbcc4dcc-b599-4e47-aef7-a1f462fcd377@intel.com> (raw)
In-Reply-To: <20241029074404.282e52b5@kernel.org>
On 10/29/2024 7:44 AM, Jakub Kicinski wrote:
> On Sat, 26 Oct 2024 12:12:45 +0800 Yue Haibing wrote:
>> v4: Target to net-next
>
> Nonetheless I'm going to assume Jake / Tony will take these.
> LMK if we should apply directly.
Yes, I'll take these through IWL.
Thanks,
Tony
next prev parent reply other threads:[~2024-10-29 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 4:12 [PATCH v4 net-next 0/4] Fix passing 0 to ERR_PTR in intel ether drivers Yue Haibing
2024-10-26 4:12 ` [Intel-wired-lan] " Yue Haibing
2024-10-26 4:12 ` [PATCH v4 net-next 1/4] igc: Fix passing 0 to ERR_PTR in igc_xdp_run_prog() Yue Haibing
2024-10-26 4:12 ` [Intel-wired-lan] " Yue Haibing
2024-10-26 15:37 ` Simon Horman
2024-10-26 15:37 ` [Intel-wired-lan] " Simon Horman
2024-11-06 13:22 ` Avigail Dahan
2024-10-26 4:12 ` [PATCH v4 net-next 2/4] igb: Fix passing 0 to ERR_PTR in igb_run_xdp() Yue Haibing
2024-10-26 4:12 ` [Intel-wired-lan] " Yue Haibing
2024-10-26 15:37 ` Simon Horman
2024-10-26 15:37 ` [Intel-wired-lan] " Simon Horman
2024-11-12 12:26 ` Rout, ChandanX
2024-11-12 12:26 ` Rout, ChandanX
2024-10-26 4:12 ` [PATCH v4 net-next 3/4] ixgbe: Fix passing 0 to ERR_PTR in ixgbe_run_xdp() Yue Haibing
2024-10-26 4:12 ` [Intel-wired-lan] " Yue Haibing
2024-10-26 15:37 ` Simon Horman
2024-10-26 15:37 ` [Intel-wired-lan] " Simon Horman
2024-11-12 12:25 ` Rout, ChandanX
2024-11-12 12:25 ` Rout, ChandanX
2024-10-26 4:12 ` [PATCH v4 net-next 4/4] ixgbevf: Fix passing 0 to ERR_PTR in ixgbevf_run_xdp() Yue Haibing
2024-10-26 4:12 ` [Intel-wired-lan] " Yue Haibing
2024-10-26 15:38 ` Simon Horman
2024-10-26 15:38 ` [Intel-wired-lan] " Simon Horman
2024-11-12 12:22 ` Rout, ChandanX
2024-11-12 12:22 ` Rout, ChandanX
2024-10-29 14:44 ` [PATCH v4 net-next 0/4] Fix passing 0 to ERR_PTR in intel ether drivers Jakub Kicinski
2024-10-29 14:44 ` [Intel-wired-lan] " Jakub Kicinski
2024-10-29 18:37 ` Tony Nguyen [this message]
2024-10-29 18:37 ` Tony Nguyen
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=bbcc4dcc-b599-4e47-aef7-a1f462fcd377@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=andre.guedes@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jithu.joseph@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sven.auhagen@voleatech.de \
--cc=vedang.patel@intel.com \
--cc=yuehaibing@huawei.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.