From: Jolly Shah <jolly.shah@xilinx.com>
To: Sudeep Holla <sudeep.holla@arm.com>, Jolly Shah <jolly.shah@xilinx.com>
Cc: ard.biesheuvel@linaro.org, mingo@kernel.org,
gregkh@linuxfoundation.org, matt@codeblueprint.co.uk,
hkallweit1@gmail.com, keescook@chromium.org,
dmitry.torokhov@gmail.com, michal.simek@xilinx.com,
rajanv@xilinx.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Tejas Patel <tejas.patel@xilinx.com>
Subject: Re: [PATCH] arch: arm64: xilinx: Make zynqmp_firmware driver optional
Date: Tue, 3 Mar 2020 14:29:57 -0800 [thread overview]
Message-ID: <8aed558b-6ff8-5c7c-626e-17f982b12682@xilinx.com> (raw)
In-Reply-To: <20200226114601.GB8613@bogus>
Hi Sudeep,
> ------Original Message------
> From: Sudeep.holla@arm.com <sudeep.holla@arm.com>
> Sent: Wednesday, February 26, 2020 3:46AM
> To: Jolly Shah <jolly.shah@xilinx.com>
> Cc: Ard.biesheuvel@linaro.org <ard.biesheuvel@linaro.org>,
Mingo@kernel.org <mingo@kernel.org>, 'Greg Kh'
<gregkh@linuxfoundation.org>, Matt@codeblueprint.co.uk
<matt@codeblueprint.co.uk>, Hkallweit1@gmail.com <hkallweit1@gmail.com>,
Keescook@chromium.org <keescook@chromium.org>, Dmitry.torokhov@gmail.com
<dmitry.torokhov@gmail.com>, Michal Simek <michal.simek@xilinx.com>,
Rajan Vaja <rajanv@xilinx.com>, Linux-arm-kernel@lists.infradead.org
<linux-arm-kernel@lists.infradead.org>, Linux-kernel@vger.kernel.org
<linux-kernel@vger.kernel.org>, Tejas Patel <tejas.patel@xilinx.com>,
Sudeep.holla@arm.com <sudeep.holla@arm.com>
> Subject: Re: [PATCH] arch: arm64: xilinx: Make zynqmp_firmware driver
optional
>
> On Tue, Feb 25, 2020 at 04:04:20PM -0800, Jolly Shah wrote:
>> From: Tejas Patel <tejas.patel@xilinx.com>
>>
>> Make zynqmp_firmware driver as optional to disable it, if user don't
>> want to use default zynqmp firmware interface.
>>
>
> This patch on it own is simple and looks fine. However I expect the
> single binary to work with and without this option on the same platform.
> If zynqmp_firmware is not critical, the system should continue to work
> fine either way. The zynqmp_firmware driver should gracefully exit with
> error(if any).
>
Sure. Will address it in next version.
Thanks,
Jolly Shah
> --
> Regards,
> Sudeep
>
next prev parent reply other threads:[~2020-03-03 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 0:04 Jolly Shah
2020-02-26 11:46 ` Sudeep Holla
2020-03-03 22:29 ` Jolly Shah [this message]
2020-03-09 13:59 ` Michal Simek
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=8aed558b-6ff8-5c7c-626e-17f982b12682@xilinx.com \
--to=jolly.shah@xilinx.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=michal.simek@xilinx.com \
--cc=mingo@kernel.org \
--cc=rajanv@xilinx.com \
--cc=sudeep.holla@arm.com \
--cc=tejas.patel@xilinx.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
all inboxes | Powered by JetHome®