Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Christian Marangi <ansuelsmth@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [net-next RFC PATCH 1/5] net: phy: move at803x PHY driver to dedicated directory
Date: Wed, 10 Jan 2024 13:43:55 +0100	[thread overview]
Message-ID: <74374085-8185-4377-ac61-e8f16d588a92@linaro.org> (raw)
In-Reply-To: <20240110115741.17300-2-ansuelsmth@gmail.com>



On 1/10/24 12:57, Christian Marangi wrote:
> In preparation for addition of other Qcom PHY and to tidy things up,
> move the at803x PHY driver to dedicated directory.
> 
> The same order in the Kconfig selection is saved.
> 
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---

This thing could use a MAINTAINERS entry too!

Konrad

  reply	other threads:[~2024-01-10 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 11:57 [net-next RFC PATCH 0/5] net: phy: split at803x Christian Marangi
2024-01-10 11:57 ` [net-next RFC PATCH 1/5] net: phy: move at803x PHY driver to dedicated directory Christian Marangi
2024-01-10 12:43   ` Konrad Dybcio [this message]
2024-01-10 11:57 ` [net-next RFC PATCH 2/5] net: phy: qcom: create and move functions to shared library Christian Marangi
2024-01-10 11:57 ` [net-next RFC PATCH 3/5] net: phy: qcom: deatch qca83xx PHY driver from at803x Christian Marangi
2024-01-10 11:57 ` [net-next RFC PATCH 4/5] net: phy: qcom: move additional functions to shared library Christian Marangi
2024-01-10 11:57 ` [net-next RFC PATCH 5/5] net: phy: qcom: detach qca808x PHY driver from at803x Christian Marangi

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=74374085-8185-4377-ac61-e8f16d588a92@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --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