From: Jiri Pirko <jiri@resnulli.us>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5][pull request] Intel Wired LAN Driver Updates 2023-02-14 (ice)
Date: Wed, 15 Feb 2023 09:03:30 +0100 [thread overview]
Message-ID: <Y+yR0oJxCl9ksx8f@nanopsycho> (raw)
In-Reply-To: <Y+yQTnI0okJU++q7@nanopsycho>
Wed, Feb 15, 2023 at 08:57:02AM CET, jiri@resnulli.us wrote:
>Tue, Feb 14, 2023 at 10:29:58PM CET, anthony.l.nguyen@intel.com wrote:
>>This series contains updates to ice driver only.
>>
>>Karol extends support for GPIO pins to E823 devices.
>>
>>Daniel Vacek stops processing of PTP packets when link is down.
>>
>>Pawel adds support for BIG TCP for IPv6.
>>
>>Tony changes return type of ice_vsi_realloc_stat_arrays() as it always
>>returns success.
>>
>>Zhu Yanjun updates kdoc stating supported TLVs.
>>
>>The following are changes since commit 2edd92570441dd33246210042dc167319a5cf7e3:
>> devlink: don't allow to change net namespace for FW_ACTIVATE reload action
>>and are available in the git repository at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue 100GbE
>>
>>Daniel Vacek (1):
>> ice/ptp: fix the PTP worker retrying indefinitely if the link went
>> down
>>
>>Karol Kolacinski (1):
>> ice: Add GPIO pin support for E823 products
>>
>>Pawel Chmielewski (1):
>> ice: add support BIG TCP on IPv6
>>
>>Tony Nguyen (1):
>> ice: Change ice_vsi_realloc_stat_arrays() to void
>>
>>Zhu Yanjun (1):
>> ice: Mention CEE DCBX in code comment
>>
>> drivers/net/ethernet/intel/ice/ice.h | 2 +
>> drivers/net/ethernet/intel/ice/ice_common.c | 25 +++++++
>> drivers/net/ethernet/intel/ice/ice_common.h | 1 +
>> drivers/net/ethernet/intel/ice/ice_dcb.c | 4 +-
>> drivers/net/ethernet/intel/ice/ice_lib.c | 11 ++--
>> drivers/net/ethernet/intel/ice/ice_main.c | 2 +
>> drivers/net/ethernet/intel/ice/ice_ptp.c | 72 ++++++++++++++++++++-
>> drivers/net/ethernet/intel/ice/ice_txrx.c | 3 +
>> 8 files changed, 109 insertions(+), 11 deletions(-)
>
>Tony, could you please send the patches alongside with the pull request,
>as for example Saeed does for mlx5 pull requests?
Ah, I see it now. Unlike 0/5, the rest got filtered out to another
folder in my inbox. Sorry :)
>
>Thanks!
next prev parent reply other threads:[~2023-02-15 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 21:29 [PATCH net-next 0/5][pull request] Intel Wired LAN Driver Updates 2023-02-14 (ice) Tony Nguyen
2023-02-14 21:29 ` [PATCH net-next 1/5] ice: Add GPIO pin support for E823 products Tony Nguyen
2023-02-14 21:30 ` [PATCH net-next 2/5] ice/ptp: fix the PTP worker retrying indefinitely if the link went down Tony Nguyen
2023-02-14 21:30 ` [PATCH net-next 3/5] ice: add support BIG TCP on IPv6 Tony Nguyen
2023-02-14 21:30 ` [PATCH net-next 4/5] ice: Change ice_vsi_realloc_stat_arrays() to void Tony Nguyen
2023-02-14 21:30 ` [PATCH net-next 5/5] ice: Mention CEE DCBX in code comment Tony Nguyen
2023-02-15 7:57 ` [PATCH net-next 0/5][pull request] Intel Wired LAN Driver Updates 2023-02-14 (ice) Jiri Pirko
2023-02-15 8:03 ` Jiri Pirko [this message]
2023-02-16 6:00 ` 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=Y+yR0oJxCl9ksx8f@nanopsycho \
--to=jiri@resnulli.us \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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