mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Parthiban.Veerasooran@microchip.com>
To: <andrew@lunn.ch>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] microchip: lan865x: fix missing ndo_eth_ioctl handler to support PHY ioctl
Date: Fri, 22 Aug 2025 13:45:43 +0000	[thread overview]
Message-ID: <6137118a-bcb6-4c4d-98bd-10e065145a60@microchip.com> (raw)
In-Reply-To: <5ac05a1f-0cd2-421c-8747-9159a62dce2b@lunn.ch>

On 22/08/25 6:29 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
>> By the way, is there a possibility to submit or apply this patch to the
>> older stable kernels as well, so that users on those versions can also
>> benefit from this feature?
> 
> This is the sort of patch the machine learning bot picks up for back
> porting to stable. The Fixes: tag is only one indicator it looks for,
> it being a one liner and the words in the commit message might trigger
> it as well.
Thank you for the explanation. As per your suggestion, I’ve moved this 
feature patch to net-next, so I assume there’s no possibility of getting 
it into the older stable kernels, as it is not a fix—is that correct?

Best regards,
Parthiban V
> 
>          Andrew


      reply	other threads:[~2025-08-22 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  8:28 Parthiban Veerasooran
2025-08-22  0:17 ` Andrew Lunn
2025-08-22  4:24   ` Parthiban.Veerasooran
2025-08-22 12:59     ` Andrew Lunn
2025-08-22 13:45       ` Parthiban.Veerasooran [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=6137118a-bcb6-4c4d-98bd-10e065145a60@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®