From: Greg KH <gregkh@linuxfoundation.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: stable@vger.kernel.org
Subject: Re: MHI v5.13 commits for stable backporting
Date: Fri, 7 May 2021 10:17:48 +0200 [thread overview]
Message-ID: <YJT3rOgd9WVvdRZl@kroah.com> (raw)
In-Reply-To: <20210507080736.GA5646@work>
On Fri, May 07, 2021 at 01:37:36PM +0530, Manivannan Sadhasivam wrote:
> Hi Greg,
>
> As suggested by you in MHI v5.13 PR [1], please find the below commits that
> got merged for v5.13 and should be backported to stable kernels:
>
> 683e77cadc83 ("bus: mhi: core: Fix shadow declarations")
> 5630c1009bd9 ("bus: mhi: pci_generic: Constify mhi_controller_config struct definitions")
> ec32332df764 ("bus: mhi: core: Sanity check values from remote device before use")
> 47705c084659 ("bus: mhi: core: Clear configuration from channel context during reset")
> 70f7025c854c ("bus: mhi: core: remove redundant initialization of variables state and ee")
> 68731852f6e5 ("bus: mhi: core: Return EAGAIN if MHI ring is full")
> 4547a749be99 ("bus: mhi: core: Fix MHI runtime_pm behavior")
> 6403298c58d4 ("bus: mhi: core: Fix check for syserr at power_up")
> 8de5ad994143 ("bus: mhi: core: Add missing checks for MMIO register entries")
> 0ecc1c70dcd3 ("bus: mhi: core: Fix invalid error returning in mhi_queue")
> 0fccbf0a3b69 ("bus: mhi: pci_generic: Remove WQ_MEM_RECLAIM flag from state workqueue")
>
> I'll make sure to tag stable list for future potential patches.
That's a lot, are you sure they are all needed? Constify?
What order should these be applied in and how far back should the
patches be backported?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-07 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 8:07 MHI v5.13 commits for stable backporting Manivannan Sadhasivam
2021-05-07 8:17 ` Greg KH [this message]
2021-05-07 10:15 ` Manivannan Sadhasivam
2021-05-07 11:22 ` Greg KH
2021-05-07 12:52 ` 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=YJT3rOgd9WVvdRZl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=manivannan.sadhasivam@linaro.org \
--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.