From: Sasha Levin <sashal@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Jian Cai <jiancai@google.com>, "# 3.4.x" <stable@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Manoj Gupta <manojgupta@google.com>,
Luis Lozano <llozano@google.com>, Arnd Bergmann <arnd@arndb.de>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Backport 44623b2818f4a442726639572f44fd9b6d0ef68c to kernel 5.4
Date: Thu, 29 Oct 2020 19:36:35 -0400 [thread overview]
Message-ID: <20201029233635.GF87646@sasha-vm> (raw)
In-Reply-To: <CAKwvOdkQ5M+ujYZgg7T80W-uNgsn_mmv8R+-15HJjPoPDpES1Q@mail.gmail.com>
On Thu, Oct 29, 2020 at 11:05:01AM -0700, Nick Desaulniers wrote:
>On Thu, Oct 29, 2020 at 4:01 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>>
>> On Mon, Oct 26, 2020 at 06:17:00PM -0700, Jian Cai wrote:
>> > Hello,
>> >
>> > I am working on assembling kernel 5.4 with LLVM's integrated assembler on
>> > ChromeOS, and the following patch is required to make it work. Would you
>> > please consider backporting it to 5.4?
>> >
>> >
>> > commit 44623b2818f4a442726639572f44fd9b6d0ef68c
>> > Author: Arnd Bergmann <arnd@arndb.de>
>> > Date: Wed May 27 16:17:40 2020 +0200
>> >
>> > crypto: x86/crc32c - fix building with clang ias
>> >
>> > Link:
>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=44623b2818f4a442726639572f44fd9b6d0ef68c
>> >
>>
>> It does not apply cleanly, can you please provide a properly backported
>> and tested version?
>
>Hi Jian,
>Thanks for proactively identifying and requesting a backport of
>44623b2818. We'll need it for Android as well soon.
>
>One thing I do when requesting backports from stable is I checkout the
>branch of the stable tree and see if the patch cherry picks cleanly.
btw, an easy way to get an idea of possible dependencies is to look at
the dependency repo :) For this commit on 5.4:
https://git.kernel.org/pub/scm/linux/kernel/git/sashal/deps.git/plain/v5.4/44623b2818f4a442726639572f44fd9b6d0ef68c
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-10-29 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+SOCLLXnxcf=bTazCT1amY7B4_37HTEXL2OwHowVGCb8SLSQQ@mail.gmail.com>
2020-10-29 11:01 ` Backport 44623b2818f4a442726639572f44fd9b6d0ef68c to kernel 5.4 Greg KH
2020-10-29 18:05 ` Nick Desaulniers
2020-10-29 23:36 ` Sasha Levin [this message]
2020-10-29 23:45 ` Nick Desaulniers
2020-10-30 0:41 ` Sasha Levin
[not found] ` <CA+SOCLJqVjy9QRssE9AZ1nQBwZB5mAcanpVTVOd4kO3=r5jrfA@mail.gmail.com>
2020-10-30 1:49 ` Nathan Chancellor
[not found] ` <CA+SOCL+b_qvvEHFz5g416Kdfzy3nZQnizow9-C9k1pw=ZeoKJA@mail.gmail.com>
2020-10-30 19:30 ` Nick Desaulniers
[not found] ` <20201030190245.92967-1-jiancai@google.com>
2020-10-30 19:06 ` [PATCH] crypto: x86/crc32c - fix building with clang ias Nick Desaulniers
2020-10-31 10:30 ` 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=20201029233635.GF87646@sasha-vm \
--to=sashal@kernel.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiancai@google.com \
--cc=llozano@google.com \
--cc=manojgupta@google.com \
--cc=ndesaulniers@google.com \
--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