netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ansuel Smith <ansuelsmth@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net PATCH 1/2] drivers: net: phy: at803x: fix resume for QCA8327 phy
Date: Sat, 9 Oct 2021 17:07:39 +0200	[thread overview]
Message-ID: <YWGwOzwhS9w5kLRx@lunn.ch> (raw)
In-Reply-To: <YWGuyLJc24zhoSp9@Ansuel-xps.localdomain>

On Sat, Oct 09, 2021 at 05:01:28PM +0200, Ansuel Smith wrote:
> On Sat, Oct 09, 2021 at 04:58:55PM +0200, Andrew Lunn wrote:
> > > It's ok. We got all confused with the Fixes tag. Pushing stuff too
> > > quickly... I should have notice they were not present in net and
> > > reporting that. Sorry for the mess.
> > 
> > It would still be good to post those fixes separate from the rest of
> > the series. I think the DT binding will need more discussion.
> > 
> >     Andrew
> 
> Considering the other phy changes are OK. Can I post the 4 phy patch
> to net-next as an unique series? (so split qca8k and phy patches)

Yes, that is fine.

     Andrew

      reply	other threads:[~2021-10-09 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 23:34 [net PATCH 1/2] drivers: net: phy: at803x: fix resume for QCA8327 phy Ansuel Smith
2021-10-08 23:34 ` [net PATCH 2/2] drivers: net: phy: at803x: add DAC amplitude fix for 8327 phy Ansuel Smith
2021-10-08 23:47 ` [net PATCH 1/2] drivers: net: phy: at803x: fix resume for QCA8327 phy Jakub Kicinski
2021-10-08 23:50   ` Ansuel Smith
2021-10-09  0:13     ` Jakub Kicinski
2021-10-09  0:16       ` Ansuel Smith
2021-10-09 14:58         ` Andrew Lunn
2021-10-09 15:01           ` Ansuel Smith
2021-10-09 15:07             ` Andrew Lunn [this message]

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=YWGwOzwhS9w5kLRx@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --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).