From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: mlevitsk@redhat.com, samuel.thibault@ens-lyon.org,
pawell@cadence.com, stable@vger.kernel.org,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, jonathanh@nvidia.com,
f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.10 000/162] 5.10.157-rc1 review
Date: Fri, 2 Dec 2022 13:39:24 +0100 [thread overview]
Message-ID: <Y4nx/HMggCOhdIMy@kroah.com> (raw)
In-Reply-To: <Y4nmNb46aqbm7JuS@duo.ucw.cz>
On Fri, Dec 02, 2022 at 12:49:09PM +0100, Pavel Machek wrote:
> Hi!
>
> [If I cc-ed you, you are author of one of patches below. Please take a
> look.]
>
> > Responses should be made by Fri, 02 Dec 2022 18:05:05 +0000.
> > Anything received after that time might be too late.
>
> I hope to make it :-). I
>
> > Pawel Laszczak <pawell@cadence.com>
> > usb: cdnsp: Device side header file for CDNSP driver
> >
> > Pawel Laszczak <pawell@cadence.com>
> > usb: cdns3: Add support for DRD CDNSP
>
> These two together are 1500+ lines, and are marked as Stable-dep-of:
> 9d5333c93134 ("usb: cdns3: host: fix endless superspeed hub port
> reset") . But we don't have that one in 5.10 tree. Likely we should
> not have these either.
I already dropped these yesterday.
> > Maxim Levitsky <mlevitsk@redhat.com>
> > KVM: x86: emulator: update the emulation mode after rsm
>
> No. The patch does not do anything. Mainline commit this referenced
> changed the return value, this changes just a comment. Wrong backport?
I will look at this.
> > Samuel Thibault <samuel.thibault@ens-lyon.org>
> > speakup: Generate speakupmap.h automatically
>
> Ok, so this one rewrites some header generation and is buggy. 500+ lines.
Already dropped yesterday.
> > Đoàn Trần Công Danh <congdanhqx@gmail.com>
> > speakup: replace utils' u_char with unsigned char
>
> With this patch fixing it. The rewrite is marked as stable depedncency
> of the fix, but fix would not be needed if we did not apply the
> rewrite. We should not have these two in stable.
Again, already dropped.
thanks for the review.
greg k-h
next prev parent reply other threads:[~2022-12-02 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 18:21 [PATCH 5.10 000/162] 5.10.157-rc1 review Greg Kroah-Hartman
2022-11-30 19:38 ` Pavel Machek
2022-11-30 20:13 ` Florian Fainelli
2022-12-01 1:01 ` Shuah Khan
2022-12-01 11:19 ` Sudip Mukherjee
2022-12-01 11:21 ` Rudi Heitbaum
2022-12-01 16:47 ` Naresh Kamboju
2022-12-02 1:44 ` Guenter Roeck
2022-12-02 11:49 ` Pavel Machek
2022-12-02 12:39 ` Greg Kroah-Hartman [this message]
2022-12-02 12:41 ` Greg Kroah-Hartman
2022-12-02 12:48 ` Jon Hunter
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=Y4nx/HMggCOhdIMy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mlevitsk@redhat.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=pawell@cadence.com \
--cc=rwarsow@gmx.de \
--cc=samuel.thibault@ens-lyon.org \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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