All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"dlemoal@kernel.org" <dlemoal@kernel.org>
Subject: Re: [PATCH 4.14.y] ata: libata: disallow dev-initiated LPM transitions to unsupported states
Date: Sat, 7 Oct 2023 11:58:34 +0200	[thread overview]
Message-ID: <2023100720-frightful-clean-4bb2@gregkh> (raw)
In-Reply-To: <ZRq+KUh8fwb8N7ru@x1-carbon>

On Mon, Oct 02, 2023 at 12:57:17PM +0000, Niklas Cassel wrote:
> On Fri, Sep 29, 2023 at 07:27:05AM +0000, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> > Hi!
> > 
> > You have forgotten the upstream commit ID.
> > And there is a message of cherry-pick -x. This is not necessary.
> > Could you please add commit ID and remove cherry-pick message?
> > 
> > commit 24e0e61db3cb86a66824531989f1df80e0939f26 upstream.
> > 
> > Best regards,
> >   Nobuhiro
> 
> Hello Nobuhiro,
> 
> The Linux 4.14 stable kernel maintainers are:
> Greg Kroah-Hartman & Sasha Levin
> 
> See:
> https://www.kernel.org/category/releases.html
> 
> I followed the instructions provided by Greg Kroah-Hartman in email:
> https://lore.kernel.org/stable/2023092002-mobster-onset-2af9@gregkh/
> 
> 
> """
> 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-4.14.y
> git checkout FETCH_HEAD
> git cherry-pick -x 24e0e61db3cb86a66824531989f1df80e0939f26
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023092002-mobster-onset-2af9@gregkh' --subject-prefix 'PATCH 4.14.y' HEAD^..
> """
> 
> 
> I do find it slightly amusing that the instructions,
> provided by none other than the stable maintainer himself,
> which mentions linux-4.14.y, should not be good enough :)
> 
> I think you should bring up your concerns with the stable
> maintainers. If this is really an issue, perhaps you can
> convince them to update their instructions.
> 
> Until then, I will assume that the provided instructions
> are satisfactory.

They are, thank you for following them, I'll go queue these up now.

greg k-h

  reply	other threads:[~2023-10-07  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  9:57 FAILED: patch "[PATCH] ata: libata: disallow dev-initiated LPM transitions to" failed to apply to 4.14-stable tree gregkh
2023-09-20 11:27 ` [PATCH] ata: libata: disallow dev-initiated LPM transitions to unsupported states Niklas Cassel
2023-09-28 15:53 ` [PATCH 4.14.y] " Niklas Cassel
2023-09-29  7:27   ` nobuhiro1.iwamatsu
2023-10-02 12:57     ` Niklas Cassel
2023-10-07  9:58       ` Greg KH [this message]
2023-10-09 23:31       ` nobuhiro1.iwamatsu
2023-10-07  9:58     ` Greg KH

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=2023100720-frightful-clean-4bb2@gregkh \
    --to=greg@kroah.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.