From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: zynqmp: Xilinx SoC changes for v4.20
Date: Sat, 8 Sep 2018 18:21:30 -0700 [thread overview]
Message-ID: <CAOesGMjh-Chhncw3cYaCvFpfhtOSz8hprC0xARmVXe8i4mvxHw@mail.gmail.com> (raw)
In-Reply-To: <5e9c248d-c19c-1881-f406-d7bfd38ec479@xilinx.com>
Hi Michal,
On Fri, Sep 7, 2018 at 12:57 AM, Michal Simek <michal.simek@xilinx.com> wrote:
> Hi,
>
> please pull the following firmware interface to your tree.
>
> Thanks,
> Michal
>
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the git repository at:
>
> https://github.com/Xilinx/linux-xlnx.git tags/zynqmp-soc-for-v4.20
>
> for you to fetch changes up to bca7067d2d4e91f58162b07d73cd94e20437b4f6:
>
> firmware: xilinx: Add debugfs for query data API (2018-09-07 09:44:44
> +0200)
>
> ----------------------------------------------------------------
> arm64: zynqmp: SoC changes for v4.20
>
> - Adding firmware API for SoC with debugfs interface
This is a bit terse. Jolly has been good at writing cover letters, you
could have stolen the writeup from there. :)
I posted two comments on the patches -- one is a nit that can be
followed up on with an incremental patch.
I'm more worried about the ioctl interface though, and what it opens
up. Maybe it's been discussed in the time the set has been reviewed, I
didn't search extensively for the history. If it had been, bringing
explanations into the patch description would have been nice for new
readers such as myself. And if it hasn't, well, let's talk about it.
Not merging based on the above. Hopefully it's something we can
straighten out pretty quickly.
-Olof
next prev parent reply other threads:[~2018-09-09 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 7:57 [GIT PULL] arm64: zynqmp: Xilinx SoC changes for v4.20 Michal Simek
2018-09-09 1:21 ` Olof Johansson [this message]
2018-09-10 12:20 ` Michal Simek
2018-09-11 15:32 ` Olof Johansson
2018-09-12 7:32 ` Michal Simek
2018-09-10 20:39 ` Jolly Shah
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=CAOesGMjh-Chhncw3cYaCvFpfhtOSz8hprC0xARmVXe8i4mvxHw@mail.gmail.com \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).