public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Sasha Levin <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Sergey Shtylyov <s.shtylyov@omp.ru>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: backport a patch of ravb for v5.10 and v5.4
Date: Mon, 16 Oct 2023 09:48:33 +0200	[thread overview]
Message-ID: <2023101647-repossess-humbling-54c3@gregkh> (raw)
In-Reply-To: <TYBPR01MB53411662F810BAA815FAF968D8D7A@TYBPR01MB5341.jpnprd01.prod.outlook.com>

On Mon, Oct 16, 2023 at 03:04:36AM +0000, Yoshihiro Shimoda wrote:
> Hello Sasha,
> 
> Thank you for backporting the latest ravb patches for stable.
> I found one of patches [1] was queued into v5.10 and v5.4 [2].
> However, another patch [3] was not queued into them. I guess
> that this is because conflict happens.
> 
> The reason for the conflict is that the condition in the following
> line is diffetent:
> ---
> v5.10 or v5.4:
> 	if (priv->chip_id != RCAR_GEN2) {
> 
> mainline:
> 	if (info->multi_irqs) {
> ---
> 
> However, this difference can be ignored when backporting. For your
> reference, I wrote a sample patch at the end of this email. Would
> you backport such a patch to v5.10 and v5.4? I would appreciate it
> if you could let me know if there is an official way to request one.
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e6864af61493113558c502b5cd0d754c19b93277
> [2] https://www.spinics.net/lists/stable-commits/msg319990.html
>     https://www.spinics.net/lists/stable-commits/msg320008.html
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3971442870713de527684398416970cf025b4f89
> 
> ---
>  drivers/net/ethernet/renesas/ravb_main.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/net/ethernet/renesas/ravb_main.c b/drivers/net/ethernet/renesas/ravb_main.c
> index a59da6a11976..f218bacec001 100644
> --- a/drivers/net/ethernet/renesas/ravb_main.c
> +++ b/drivers/net/ethernet/renesas/ravb_main.c
> @@ -1706,6 +1706,8 @@ static int ravb_close(struct net_device *ndev)
>  			of_phy_deregister_fixed_link(np);
>  	}
>  
> +	cancel_work_sync(&priv->work);
> +
>  	if (priv->chip_id != RCAR_GEN2) {
>  		free_irq(priv->tx_irqs[RAVB_NC], ndev);
>  		free_irq(priv->rx_irqs[RAVB_NC], ndev);
> -- 
> 2.25.1
> 

Can you please just send a working backport for the kernel trees you
wish to see this applied to?  Merging patches like this is not easy and
doesn't usually result in a commit that we know actually works properly.

thanks,

greg k-h

  reply	other threads:[~2023-10-16  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16  3:04 backport a patch of ravb for v5.10 and v5.4 Yoshihiro Shimoda
2023-10-16  7:48 ` Greg KH [this message]
2023-10-16  9:28   ` Yoshihiro Shimoda

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=2023101647-repossess-humbling-54c3@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=s.shtylyov@omp.ru \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.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