From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Pavel Machek <pavel@denx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
richard.weiyang@gmail.com, masahiroy@kernel.org,
ojeda@kernel.org, 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, conor@kernel.org,
allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/244] 6.1.91-rc3 review
Date: Fri, 17 May 2024 12:41:04 +0200 [thread overview]
Message-ID: <CANiq72k_JQVy=xYeFYb4h-gds=_4HPcV_1uBmUnaveSXVBPkdA@mail.gmail.com> (raw)
In-Reply-To: <ZkYCYxoxqrwlVSI5@duo.ucw.cz>
On Thu, May 16, 2024 at 2:56 PM Pavel Machek <pavel@denx.de> wrote:
>
> These are marked as Stable-dep-of: ded103c7eb23 ("kbuild: rust: force
> `alloc` extern to allow "empty" Rust files"), but we don't have
> ded103c7eb23 in 6.1-stable, so we should not need these.
I think what happened is that I asked for ded103c7eb23 to be dropped,
but its deps didn't get dropped.
Having said that, "kbuild: specify output names" was a fix in its own,
so we may want to keep it anyway (with its fix).
Cheers,
Miguel
next prev parent reply other threads:[~2024-05-17 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 9:13 [PATCH 6.1 000/244] 6.1.91-rc3 review Greg Kroah-Hartman
2024-05-16 10:44 ` Pavel Machek
2024-05-16 12:22 ` Mark Brown
2024-05-16 12:33 ` Jon Hunter
2024-05-16 12:56 ` Pavel Machek
2024-05-17 10:41 ` Miguel Ojeda [this message]
2024-05-16 16:43 ` SeongJae Park
2024-05-16 16:57 ` Florian Fainelli
2024-05-16 19:35 ` Shreeya Patel
2024-05-17 0:29 ` Allen
2024-05-17 10:25 ` Naresh Kamboju
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='CANiq72k_JQVy=xYeFYb4h-gds=_4HPcV_1uBmUnaveSXVBPkdA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=richard.weiyang@gmail.com \
--cc=rwarsow@gmx.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).