Re: [PATCH 4.14.y] ata: libata: disallow dev-initiated LPM transitions to unsupported states

[Niklas Cassel <Niklas.Cassel@wdc.com>]

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.


Kind regards,
Niklas