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: <20190409180143.GZ9224@smile.fi.intel.com>
Date:   Tue, 9 Apr 2019 21:01:43 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     Vinod Koul <vkoul@...nel.org>, dmaengine@...r.kernel.org,
        Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] dmaengine: idma64: Move driver name to the header

On Tue, Apr 09, 2019 at 09:37:28AM -0700, Christoph Hellwig wrote:
> On Tue, Apr 09, 2019 at 06:02:19PM +0300, Andy Shevchenko wrote:
> > There are two drivers that are relying on the iDMA 64-bit driver name
> > to match. Instead of duplicating string in both of them, dedicate
> > a header file and share it between users.
> 
> Hmm.  Why do we have two separate drivers for the same name?
> 
> Something is rather fishy there.

We would like to be sure that the DMA controller driver is loaded before its
consumers.

-- 
With Best Regards,
Andy Shevchenko


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ