From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Qian Cai <quic_qiancai@quicinc.com>
Subject: Re: [GIT PULL] arm64 fixes for -rc6
Date: Wed, 15 Dec 2021 16:00:17 +0000 [thread overview]
Message-ID: <YboRETjutObrQTHH@arm.com> (raw)
In-Reply-To: <20211215111917.GB16765@willie-the-truck>
Hi Linus,
On Wed, Dec 15, 2021 at 11:19:18AM +0000, Will Deacon wrote:
> Please pull this pair of arm64 fixes for -rc6. There's a fix for missing
> locking around kernel page-table allocation causing a crash with
> virtio-mem and a fix for a smatch warning in the kexec code where we
> would return 0 on the error path.
[...]
> ----------------------------------------------------------------
> Jianyong Wu (1):
> arm64/mm: Avoid fixmap race condition when creating pud mappings
I you haven't pulled this yet, please discard the request. I'll revert
the above commit as it causes a regression, reported here:
https://lore.kernel.org/all/Ybn4EfweLqKtyW0+@fixkernel.com/
Will is already on holiday, so I'll retag the branch tomorrow and send a
new pull request.
Thanks and sorry for the trouble.
--
Catalin
next prev parent reply other threads:[~2021-12-15 16:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:19 [GIT PULL] arm64 fixes for -rc6 Will Deacon
2021-12-15 16:00 ` Catalin Marinas [this message]
2021-12-15 18:49 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 10:25 Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-06-20 16:59 [GIT PULL] arm64: fixes " Will Deacon
2019-06-20 19:10 ` pr-tracker-bot
2019-02-08 17:35 Will Deacon
2019-02-09 0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-12 9:14 ` Will Deacon
2017-04-12 10:18 ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 Will Deacon
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=YboRETjutObrQTHH@arm.com \
--to=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_qiancai@quicinc.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).