From: James Morse <james.morse@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>, Will Deacon <will@kernel.org>,
Christoph Hellwig <hch@lst.de>, Hanjun Guo <guohanjun@huawei.com>
Subject: [PATCH 0/3] firmare: arm_sdei: Extras for v5.8
Date: Tue, 19 May 2020 19:21:05 +0100 [thread overview]
Message-ID: <20200519182108.13693-1-james.morse@arm.com> (raw)
Hi Will, Catalin,
Some extra patches for SDEI if you're still willing to add to your tree.
Hanjun's patch to cleanup some ACPI table handling conflicts with
Sudeep's patch that you already have queued.
Based on arm64's for-next/sdei branch: v5.7-rc3-1-gcaf2cd610dbb
For the tag, I'd describe all four patches as:
---
Cleanup the driver probing, remove some unused module exports and document
the reason behind a set_fs() call.
---
Thanks,
James
Christoph Hellwig (1):
firmware: arm_sdei: remove unused interfaces
Hanjun Guo (1):
firmware: arm_sdei: Put the SDEI table after using it
James Morse (1):
firmware: arm_sdei: Document the motivation behind these set_fs()
calls
drivers/firmware/arm_sdei.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
--
2.19.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-05-19 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 18:21 James Morse [this message]
2020-05-19 18:21 ` [PATCH 1/3] firmware: arm_sdei: Put the SDEI table after using it James Morse
2020-05-19 18:21 ` [PATCH 2/3] firmware: arm_sdei: remove unused interfaces James Morse
2020-05-19 18:21 ` [PATCH 3/3] firmware: arm_sdei: Document the motivation behind these set_fs() calls James Morse
2020-05-20 11:00 ` [PATCH 0/3] firmare: arm_sdei: Extras for v5.8 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=20200519182108.13693-1-james.morse@arm.com \
--to=james.morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.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