From: Leon Romanovsky <leon@kernel.org>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, mengyuanlou@net-swift.com
Subject: Re: [PATCH net v2 0/5] net: wangxun: Adjust code structure
Date: Wed, 14 Dec 2022 09:58:01 +0200 [thread overview]
Message-ID: <Y5mCCQ3mrwD/gSSi@unreal> (raw)
In-Reply-To: <20221214064133.2424570-1-jiawenwu@trustnetic.com>
On Wed, Dec 14, 2022 at 02:41:28PM +0800, Jiawen Wu wrote:
> Remove useless structs 'txgbe_hw' and 'ngbe_hw' make the codes clear.
> And move the same codes which sets MAC address between txgbe and ngbe
> to libwx.
>
> Changelog:
> v2:
> - Split patch v1 into separate patches
> - Fix unreasonable code logic in MAC address operations
>
> Jiawen Wu (5):
> net: txgbe: Remove structure txgbe_hw
> net: ngbe: Remove structure ngbe_hw
> net: txgbe: Move defines into unified file
> net: ngbe: Move defines into unified file
> net: wangxun: Move MAC address handling to libwx
>
From Jakub (copy/paste):
# Form letter - net-next is closed
We have already submitted the networking pull request to Linus
for v6.2 and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after 6.2-rc1 is cut.
Thanks
next prev parent reply other threads:[~2022-12-14 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 6:41 [PATCH net v2 0/5] net: wangxun: Adjust code structure Jiawen Wu
2022-12-14 6:41 ` [PATCH net v2 1/5] net: txgbe: Remove structure txgbe_hw Jiawen Wu
2022-12-14 6:41 ` [PATCH net v2 2/5] net: ngbe: Remove structure ngbe_hw Jiawen Wu
2022-12-21 13:55 ` Andrew Lunn
2022-12-14 6:41 ` [PATCH net v2 3/5] net: txgbe: Move defines into unified file Jiawen Wu
2022-12-14 6:41 ` [PATCH net v2 4/5] net: ngbe: " Jiawen Wu
2022-12-14 6:41 ` [PATCH net v2 5/5] net: wangxun: Move MAC address handling to libwx Jiawen Wu
2022-12-14 7:58 ` Leon Romanovsky [this message]
2022-12-14 16:44 ` [PATCH net v2 0/5] net: wangxun: Adjust code structure Alexander H Duyck
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=Y5mCCQ3mrwD/gSSi@unreal \
--to=leon@kernel.org \
--cc=jiawenwu@trustnetic.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).