From: Sasha Levin <sashal@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 6/8] radix tree test suite: Fix compilation
Date: Wed, 14 Apr 2021 08:18:46 -0400 [thread overview]
Message-ID: <YHbdpo3dP1INDp0z@sashalap> (raw)
In-Reply-To: <20210405181109.GH2531743@casper.infradead.org>
On Mon, Apr 05, 2021 at 07:11:09PM +0100, Matthew Wilcox wrote:
>On Mon, Apr 05, 2021 at 12:05:13PM -0400, Sasha Levin wrote:
>> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>>
>> [ Upstream commit dd841a749d1ded8e2e5facc4242ee0b6779fc0cb ]
>>
>> Introducing local_lock broke compilation; fix it all up.
>
>I don't think local_lock has been backported to 4.19?
Heh, right, I'll drop it from 5.4 and older.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-04-14 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 16:05 [PATCH AUTOSEL 4.19 1/8] KVM: arm64: Hide system instruction access to Trace registers Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 2/8] KVM: arm64: Disable guest access to trace filter controls Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 3/8] drm/imx: imx-ldb: fix out of bounds array access warning Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 4/8] gfs2: report "already frozen/thawed" errors Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 5/8] drm/tegra: dc: Don't set PLL clock to 0Hz Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 6/8] radix tree test suite: Fix compilation Sasha Levin
2021-04-05 18:11 ` Matthew Wilcox
2021-04-14 12:18 ` Sasha Levin [this message]
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 7/8] block: only update parent bi_status when bio fail Sasha Levin
2021-04-05 16:05 ` [PATCH AUTOSEL 4.19 8/8] riscv,entry: fix misaligned base for excp_vect_table 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=YHbdpo3dP1INDp0z@sashalap \
--to=sashal@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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