public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Enguerrand de Ribaucourt 
	<enguerrand.de-ribaucourt@savoirfairelinux.com>
Cc: stable@vger.kernel.org, andrew@lunn.ch
Subject: Re: [PATCH v3 0/2] net: dp83822: backport fix interrupt floods
Date: Thu, 8 Sep 2022 19:07:47 +0200	[thread overview]
Message-ID: <YxohY8Loyg3SBuld@kroah.com> (raw)
In-Reply-To: <20220907104558.256807-1-enguerrand.de-ribaucourt@savoirfairelinux.com>

On Wed, Sep 07, 2022 at 12:45:57PM +0200, Enguerrand de Ribaucourt wrote:
> This series backports the following fixes from 5.10 to 5.4.
> This backport should also apply to 4.19.
> 
> A git conflict was solved involving DP83822_ANEG_COMPLETE_INT_EN which was moved
> to a conditional in 5.10.
> 
> Original commit IDs:
> c96614eeab663646f57f67aa591e015abd8bd0ba net: dp83822: disable false carrier interrupt
> 0e597e2affb90d6ea48df6890d882924acf71e19 net: dp83822: disable rx error interrupt
> 
> 

These are alread in 5.10.y, they showed up in 5.10.129.  Should I just
take these into 5.4.y and 4.19.y instead?

thanks,

greg k-h

  parent reply	other threads:[~2022-09-08 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 10:45 [PATCH v3 0/2] net: dp83822: backport fix interrupt floods Enguerrand de Ribaucourt
2022-09-07 10:45 ` [PATCH v3 1/2] net: dp83822: disable false carrier interrupt Enguerrand de Ribaucourt
2022-09-07 10:45 ` [PATCH v3 2/2] net: dp83822: disable rx error interrupt Enguerrand de Ribaucourt
2022-09-08 17:09   ` Greg KH
2022-09-12 10:07     ` Enguerrand de Ribaucourt
2022-09-12 14:39       ` Greg KH
2022-09-13  8:17       ` [PATCH v3] " Enguerrand de Ribaucourt
2022-09-13 11:30         ` Greg KH
2022-09-14  7:07           ` Enguerrand de Ribaucourt
2022-09-16  9:35             ` Greg KH
2022-09-08 17:07 ` Greg KH [this message]
2022-09-12 10:02   ` [PATCH v3 0/2] net: dp83822: backport fix interrupt floods Enguerrand de Ribaucourt

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=YxohY8Loyg3SBuld@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=enguerrand.de-ribaucourt@savoirfairelinux.com \
    --cc=stable@vger.kernel.org \
    /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