linux-kernel - RE: [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CY1PR02MB21380A6ED51FD3C8C75EB309B8170@CY1PR02MB2138.namprd02.prod.outlook.com>
Date:   Mon, 24 Sep 2018 18:21:55 +0000
From:   Jolly Shah <JOLLYS@...inx.com>
To:     Olof Johansson <olof@...om.net>
CC:     Michal Simek <michals@...inx.com>,
        "arm@...nel.org" <arm@...nel.org>, Rajan Vaja <RAJANV@...inx.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP
 core

Hi Olof,

> -----Original Message-----
> From: Olof Johansson [mailto:olof@...om.net]
> Sent: Sunday, September 23, 2018 6:13 AM
> To: Jolly Shah <JOLLYS@...inx.com>
> Cc: Michal Simek <michals@...inx.com>; arm@...nel.org; Rajan Vaja
> <RAJANV@...inx.com>; linux-arm-kernel@...ts.infradead.org; linux-
> kernel@...r.kernel.org
> Subject: Re: [PATCH v12 0/6] drivers: Introduce firmware driver for ZynqMP core
> 
> On Thu, Sep 20, 2018 at 5:46 PM, Jolly Shah <JOLLYS@...inx.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.
> 

Sounds good. I will make required changes and submit as incremental patches along with clock driver.

> 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.
> 
> 

Thanks. Michal will create pull request for same.

Thanks,
Jolly Shah

> 
> -Olof