From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Liang Xu <lxu@maxlinear.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"hkallweit1@gmail.com" <hkallweit1@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"vee.khee.wong@linux.intel.com" <vee.khee.wong@linux.intel.com>,
Hauke Mehrtens <hmehrtens@maxlinear.com>,
Thomas Mohren <tmohren@maxlinear.com>,
"mohammad.athari.ismail@intel.com"
<mohammad.athari.ismail@intel.com>
Subject: Re: [PATCH v5 2/2] net: phy: add Maxlinear GPY115/21x/24x driver
Date: Tue, 6 Jul 2021 16:44:54 +0100 [thread overview]
Message-ID: <20210706154454.GR22278@shell.armlinux.org.uk> (raw)
In-Reply-To: <7e2b16b4-839c-0e1d-4d36-3b3fbf5be9eb@maxlinear.com>
On Tue, Jul 06, 2021 at 03:34:56PM +0000, Liang Xu wrote:
> On 1/7/2021 4:26 pm, Xu Liang wrote:
> > Add driver to support the Maxlinear GPY115, GPY211, GPY212, GPY215,
> > GPY241, GPY245 PHYs. Separate from XWAY PHY driver because this series
> > has different register layout and new features not supported in XWAY PHY.
> >
> > Signed-off-by: Xu Liang <lxu@maxlinear.com>
> > ---
> > v2 changes:
> > Fix format warning from checkpath and some comments.
> > Use smaller PHY ID mask.
> > Split FWV register mask.
> > Call phy_trigger_machine if necessary when clear interrupt.
> > v3 changes:
> > Replace unnecessary phy_modify_mmd_changed with phy_modify_mmd
> > Move firmware version print to probe.
> > v4 changes:
> > Separate PHY ID for new silicon.
> > Use full Maxlinear name in Kconfig.
> > Add and use C45 ID read API, and use genphy_c45_pma_read_abilities.
> > Use my name instead of company as author.
> > v5 changes:
> > Fix comment for link speed 2.5G.
>
> Hi Andrew,
>
>
> Need your help on this patch.
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20210701082658.21875-1-lxu@maxlinear.com/
>
> I see the status is "Not applicable" and description "Guessing tree name
> failed - patch did not apply".
>
> How should I fix the problem?
For netdev, the subject line should contain the tree that you want
the patch applied to.
So, "[PATCH net n/N] ..." or "[PATCH net-next n/N] ..."
In this case, because it isn't a fix, you want net-next. However, as
we are in the upstream merge window, the net-next tree is currently
closed to new submissions. Please wait until it has reopened, which
will after -rc1 has been released.
You can check the current status of net-next at:
http://vger.kernel.org/~davem/net-next.html
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-07-06 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 8:26 [PATCH v5 1/2] net: phy: add API to read 802.3-c45 IDs Xu Liang
2021-07-01 8:26 ` [PATCH v5 2/2] net: phy: add Maxlinear GPY115/21x/24x driver Xu Liang
2021-07-06 15:34 ` Liang Xu
2021-07-06 15:44 ` Russell King (Oracle) [this message]
[not found] ` <c4772ca8-42e3-9c9d-2388-e19acb19e073@maxlinear.com>
2021-07-07 15:22 ` Andrew Lunn
2021-07-08 5:04 ` Liang Xu
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=20210706154454.GR22278@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=hmehrtens@maxlinear.com \
--cc=kuba@kernel.org \
--cc=lxu@maxlinear.com \
--cc=mohammad.athari.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=tmohren@maxlinear.com \
--cc=vee.khee.wong@linux.intel.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).