From: Will Deacon <will@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Thomas Tai <thomas.tai@oracle.com>,
Tom Saeger <tom.saeger@oracle.com>,
linux-doc@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Randy Dunlap <rdunlap@infradead.org>,
Al Stone <al.stone@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: arm64/acpi : clarify arm64 support of IBFT
Date: Mon, 22 Mar 2021 13:19:59 +0000 [thread overview]
Message-ID: <161641700110.3900554.4306809050769717911.b4-ty@kernel.org> (raw)
In-Reply-To: <9efc652df2b8d6b53d9acb170eb7c9ca3938dfef.1615920441.git.tom.saeger@oracle.com>
On Tue, 16 Mar 2021 12:50:41 -0600, Tom Saeger wrote:
> In commit 94bccc340710 ("iscsi_ibft: make ISCSI_IBFT dependson ACPI instead
> of ISCSI_IBFT_FIND") Kconfig was disentangled to make ISCSI_IBFT selection
> not depend on x86.
>
> Update arm64 acpi documentation, changing IBFT support status from
> "Not Supported" to "Optional".
> Opportunistically re-flow paragraph for changed lines.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] Documentation: arm64/acpi : clarify arm64 support of IBFT
https://git.kernel.org/arm64/c/e14a371f732b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-03-22 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 18:50 [PATCH] Documentation: arm64/acpi : clarify arm64 support of IBFT Tom Saeger
2021-03-16 19:46 ` Konrad Rzeszutek Wilk
2021-03-18 10:44 ` Will Deacon
2021-03-18 11:29 ` Lorenzo Pieralisi
2021-03-18 14:20 ` Ard Biesheuvel
2021-03-22 11:33 ` Lorenzo Pieralisi
2021-03-22 13:19 ` Will Deacon [this message]
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=161641700110.3900554.4306809050769717911.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=al.stone@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=kernel-team@android.com \
--cc=konrad@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=thomas.tai@oracle.com \
--cc=tom.saeger@oracle.com \
/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