public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Wolfram Sang'" <wsa@kernel.org>,
	"'Russell King \(Oracle\)'" <linux@armlinux.org.uk>
Cc: <netdev@vger.kernel.org>, <jarkko.nikula@linux.intel.com>,
	<andriy.shevchenko@linux.intel.com>,
	<mika.westerberg@linux.intel.com>, <jsd@semihalf.com>,
	<Jose.Abreu@synopsys.com>, <andrew@lunn.ch>,
	<hkallweit1@gmail.com>, <linux-i2c@vger.kernel.org>,
	<linux-gpio@vger.kernel.org>, <mengyuanlou@net-swift.com>,
	"'Piotr Raczynski'" <piotr.raczynski@intel.com>
Subject: RE: [PATCH net-next v11 2/9] i2c: designware: Add driver support for Wangxun 10Gb NIC
Date: Tue, 6 Jun 2023 09:58:54 +0800	[thread overview]
Message-ID: <018701d9981a$7278a0a0$5769e1e0$@trustnetic.com> (raw)
In-Reply-To: <ZH3bwBZvjyIoFaVv@shikoro>

On Monday, June 5, 2023 8:58 PM, Wolfram Sang wrote:
> > Be careful... net-next uses patchwork, and I suspect as this is posted
> > as a series which the subject line states as being destined by the
> > author for the "net-next" tree, the entire series will end up being
> > slurped into the net-next tree.
> 
> Thanks for the pointer. Jiawen Wu, would you kindly send a v12 of the
> series (without the I2C patch)?

Okay, v12 series will be other 8 patches for net-next.
Do I need to send this independent patch to I2C tree?


  parent reply	other threads:[~2023-06-06  1:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  2:52 [PATCH net-next v11 0/9] TXGBE PHYLINK support Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 1/9] net: txgbe: Add software nodes to support phylink Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 2/9] i2c: designware: Add driver support for Wangxun 10Gb NIC Jiawen Wu
2023-06-05  7:02   ` Wolfram Sang
2023-06-05  7:23     ` Jiawen Wu
2023-06-05  7:52       ` 'Wolfram Sang'
2023-06-05  8:12         ` Jiawen Wu
2023-06-05 10:05           ` 'Wolfram Sang'
2023-06-05 10:18             ` Russell King (Oracle)
2023-06-05 12:57               ` 'Wolfram Sang'
2023-06-05 13:03                 ` Andy Shevchenko
2023-06-05 21:25                   ` Jakub Kicinski
2023-06-06  1:58                 ` Jiawen Wu [this message]
2023-06-06  5:26                   ` 'Wolfram Sang'
2023-06-05  8:10   ` Jarkko Nikula
2023-06-05  2:52 ` [PATCH net-next v11 3/9] net: txgbe: Register fixed rate clock Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 4/9] net: txgbe: Register I2C platform device Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 5/9] net: txgbe: Add SFP module identify Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 6/9] net: txgbe: Support GPIO to SFP socket Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 7/9] net: pcs: Add 10GBASE-R mode for Synopsys Designware XPCS Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 8/9] net: txgbe: Implement phylink pcs Jiawen Wu
2023-06-05  2:52 ` [PATCH net-next v11 9/9] net: txgbe: Support phylink MAC layer Jiawen Wu

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='018701d9981a$7278a0a0$5769e1e0$@trustnetic.com' \
    --to=jiawenwu@trustnetic.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=andrew@lunn.ch \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hkallweit1@gmail.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mengyuanlou@net-swift.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=piotr.raczynski@intel.com \
    --cc=wsa@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