From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Rodríguez Barbarin, José Javier" <josejavier.rodriguez@duagon.com>
Cc: "sashal@kernel.org" <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"jth@kernel.org" <jth@kernel.org>,
"Sanjuán García, Jorge" <Jorge.SanjuanGarcia@duagon.com>,
"morbidrsa@gmail.com" <morbidrsa@gmail.com>
Subject: Re: Missing patches of a patch series during AUTOSEL backport
Date: Tue, 24 Oct 2023 15:59:25 +0200 [thread overview]
Message-ID: <2023102450-designed-cosmic-1bb2@gregkh> (raw)
In-Reply-To: <aa7145b39b72237a7cfd9ab8ba92ad26271f4881.camel@duagon.com>
On Tue, Oct 24, 2023 at 01:02:39PM +0000, Rodríguez Barbarin, José Javier wrote:
> Dear Sasha Levin,
>
> I am the author of a patch series and I am writting you because I have
> detected an issue with a patch series I have submitted in May'23.
>
> I sent a series of 3 patches to the maintainer. When he approved them,
> he sent an email to Greg, requesting him to include such
> patch series in kernel 6.4.
>
> You can check the email thread here:
>
> https://lore.kernel.org/all/20230411083329.4506-1-jth@kernel.org/
I totally missed that patch thread as there was no git commit ids in it,
sorry.
> For a reason I cannot understand, the AUTOSEL only chose 1 of 3 patches
> of the series, so only 1 was backported to stable kernel versions.
>
> [PATCH AUTOSEL 6.3 24/24] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 6.2 20/20] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 6.1 19/19] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 5.15 10/10] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 5.10 9/9] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 5.4 9/9] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 4.19 9/9] mcb-pci: Reallocate memory region to avoid
> memory overlapping
> [PATCH AUTOSEL 4.14 8/8] mcb-pci: Reallocate memory region to avoid
> memory overlapping
>
> In kernel 6.4 and above, the 3 patches were included.
autosel comes along later and decided that some of them were to be
included, that was independent of your email.
> Including only 1 patch is causing crashes in part of our devices.
>
> Please, could you backport the remaining 2 patches to the stable
> versions?
What is the git commit ids that you are asking for to be applied?
That's a requirement for us to take stuff.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-24 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 13:02 Missing patches of a patch series during AUTOSEL backport Rodríguez Barbarin, José Javier
2023-10-24 13:59 ` gregkh [this message]
2023-10-24 14:54 ` Rodríguez Barbarin, José Javier
2023-10-24 14:31 ` Sasha Levin
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=2023102450-designed-cosmic-1bb2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jorge.SanjuanGarcia@duagon.com \
--cc=josejavier.rodriguez@duagon.com \
--cc=jth@kernel.org \
--cc=morbidrsa@gmail.com \
--cc=sashal@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox