netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: David Miller <davem@davemloft.net>,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH] net: dsa: allow XAUI phy interface mode
Date: Tue, 12 Dec 2017 09:35:56 +0100	[thread overview]
Message-ID: <20171212083556.GN28672@lunn.ch> (raw)
In-Reply-To: <20171211190220.GY10595@n2100.armlinux.org.uk>

> That's something like it - asked Andrew via IRC on Saturday:
> 
> Do we want to do the XAUI thing as one patch to avoid any breakage, and
> if so via whom?

Hi Russell

Sorry for not replying. I was on a plane by then.

> and haven't had a response.  Normally arm-soc folk want patches
> touching arch/arm/boot/dts to go via their tree.
> 
> So, until I know what to do, I can't proceed with this... and I've
> soo many outstanding net patches now that I'm losing track of where
> each patch I've sent out is.  Sorry, I'm failing.

I would put both patches via netdev, to avoid breakage. We have done
this before for the ZII devel board, with the imx maintainers ACK.  I
don't expect any clashes in the DT file. The 10Gb port might be added
soon, but i think there is enough separation in the changes they won't
result in a conflict if they take a different path.

Do you want me to send a v2, with the additional DT patch?

   Thanks
	Andrew

      reply	other threads:[~2017-12-12  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08 16:04 [PATCH] net: dsa: allow XAUI phy interface mode Russell King
2017-12-08 16:26 ` Andrew Lunn
2017-12-08 16:42   ` Russell King - ARM Linux
2017-12-09 19:08     ` Andrew Lunn
2017-12-11 18:54 ` David Miller
2017-12-11 19:02   ` Russell King - ARM Linux
2017-12-12  8:35     ` 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=20171212083556.GN28672@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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;
as well as URLs for NNTP newsgroup(s).