From: Olof Johansson <olof@lixom.net>
To: Jolly Shah <JOLLYS@xilinx.com>
Cc: Michal Simek <michals@xilinx.com>,
"arm@kernel.org" <arm@kernel.org>, 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>
Subject: Re: [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core
Date: Sun, 23 Sep 2018 14:13:23 +0100 [thread overview]
Message-ID: <CAOesGMgUaQMcTQsbLR_qN95QPfOE1gCJuM9=6AiFLg+_t98qaw@mail.gmail.com> (raw)
In-Reply-To: <CY1PR02MB21385F71D8BC4498654CD0BFB8130@CY1PR02MB2138.namprd02.prod.outlook.com>
On Thu, Sep 20, 2018 at 5:46 PM, Jolly Shah <JOLLYS@xilinx.com> wrote:
> Hi Olof,
>
> As suggested, this patchset is generated without ioctl interface. Please review. If you are ok, Michal can create a pull request for merge.
Hi,
I replied on the other thread as well; it sounds like you will need
something _like_ the ioctl interface for some of the dependent
drivers. For those, would it be possible to only expose some of the
ioctls through the interface, and not just pass through any call? I
think that'd probably take care of my concern.
But yeah, go ahead and stage these in a pull request for now, that way
we can take care of these and merge them as the rest are getting
ready. I don't want to hold you up more than needed; the patch set is
already up to a very high version number and it's not fair to make you
rework it completely yet again.
-Olof
next prev parent reply other threads:[~2018-09-23 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 19:38 [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core Jolly Shah
2018-09-12 19:38 ` [PATCH v12 1/6] dt-bindings: firmware: Add bindings for ZynqMP firmware Jolly Shah
2018-09-12 19:38 ` [PATCH v12 2/6] firmware: xilinx: Add Zynqmp firmware driver Jolly Shah
2018-09-12 19:38 ` [PATCH v12 3/6] firmware: xilinx: Add query data API Jolly Shah
2018-09-12 19:38 ` [PATCH v12 4/6] firmware: xilinx: Add clock APIs Jolly Shah
2018-09-12 19:38 ` [PATCH v12 5/6] firmware: xilinx: Add debugfs interface Jolly Shah
2018-09-12 19:38 ` [PATCH v12 6/6] firmware: xilinx: Add debugfs for query data API Jolly Shah
2018-09-20 16:46 ` [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core Jolly Shah
2018-09-23 13:13 ` Olof Johansson [this message]
2018-09-24 18:21 ` Jolly Shah
2018-09-26 18:25 ` 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='CAOesGMgUaQMcTQsbLR_qN95QPfOE1gCJuM9=6AiFLg+_t98qaw@mail.gmail.com' \
--to=olof@lixom.net \
--cc=JOLLYS@xilinx.com \
--cc=RAJANV@xilinx.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@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;
as well as URLs for NNTP newsgroup(s).