From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Paolo Abeni'" <pabeni@redhat.com>,
"'Russell King'" <linux@armlinux.org.uk>
Cc: <netdev@vger.kernel.org>
Subject: RE: net vs net-next conflicts while cross merging
Date: Wed, 20 Nov 2024 16:28:32 +0800 [thread overview]
Message-ID: <013a01db3b26$2f719310$8e54b930$@trustnetic.com> (raw)
In-Reply-To: <f769256c-d51c-4983-b7a5-015add42ca35@redhat.com>
On Tue, No 19, 2024 9:15 PM, Paolo Abeni wrote:
> Hi,
>
> I just cross-merged net into net-next for the 6.13 PR. There was 2
> conflicts:
>
> include/linux/phy.h
> 41ffcd95015f net: phy: fix phylib's dual eee_enabled
> 21aa69e708b net: phy: convert eee_broken_modes to a linkmode bitmap
>
> drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c
> 2160428bcb20 net: txgbe: fix null pointer to pcs
> 2160428bcb20 net: txgbe: remove GPIO interrupt controller
Hi,
I don't find what's the conflict here. Do you mean these two:
2160428bcb20 ("net: txgbe: fix null pointer to pcs")
155c499ffd1d ("net: wangxun: txgbe: use phylink_pcs internally")
If this is the case, it should be resolved as follow:
static struct phylink_pcs *txgbe_phylink_mac_select(struct phylink_config *config,
phy_interface_t interface)
{
struct wx *wx = phylink_to_wx(config);
struct txgbe *txgbe = wx->priv;
if (wx->media_type != sp_media_copper)
return txgbe->pcs;
return NULL;
}
Thanks!
next prev parent reply other threads:[~2024-11-20 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 13:15 net vs net-next conflicts while cross merging Paolo Abeni
2024-11-19 13:29 ` Russell King (Oracle)
2024-11-20 8:28 ` Jiawen Wu [this message]
2024-11-20 8:45 ` Paolo Abeni
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='013a01db3b26$2f719310$8e54b930$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--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;
as well as URLs for NNTP newsgroup(s).