From: Greg KH <gregkh@linuxfoundation.org>
To: Florian Bezdeka <florian@bezdeka.de>
Cc: yoong.siang.song@intel.com, anthony.l.nguyen@intel.com,
brouer@redhat.com, davem@davemloft.net, jacob.e.keller@intel.com,
leonro@nvidia.com, naamax.meir@linux.intel.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] igc: read before write to SRRCTL register" failed to apply to 6.1-stable tree
Date: Thu, 11 May 2023 07:45:31 +0900 [thread overview]
Message-ID: <2023051115-width-squeeze-319b@gregkh> (raw)
In-Reply-To: <46a3afc2-4b15-cb2d-b257-15e8928b8eec@bezdeka.de>
On Thu, May 11, 2023 at 12:01:36AM +0200, Florian Bezdeka wrote:
> Hi all,
>
> On 07.05.23 08:44, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 6.1-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > To reproduce the conflict and resubmit, you may use the following commands:
> >
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 3ce29c17dc847bf4245e16aad78a7617afa96297
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023050749-deskwork-snowboard-82cf@gregkh' --subject-prefix 'PATCH 6.1.y' HEAD^..
>
> Is someone already working on that? I would love to see this patch in
> 6.1. If no further activities are planned I might have the option/time
> to supply a backport as well.
Please supply a backport, I don't think anyone is working on it :)
next prev parent reply other threads:[~2023-05-10 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 6:44 FAILED: patch "[PATCH] igc: read before write to SRRCTL register" failed to apply to 6.1-stable tree gregkh
2023-05-10 22:01 ` Florian Bezdeka
2023-05-10 22:45 ` Greg KH [this message]
2023-05-11 6:56 ` Song, Yoong Siang
2023-05-15 18:13 ` florian
2023-05-16 2:05 ` Song, Yoong Siang
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=2023051115-width-squeeze-319b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anthony.l.nguyen@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=florian@bezdeka.de \
--cc=jacob.e.keller@intel.com \
--cc=leonro@nvidia.com \
--cc=naamax.meir@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=yoong.siang.song@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