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: <20170705203335.GA10792@infradead.org>
Date:   Wed, 5 Jul 2017 13:33:35 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Helge Deller <deller@....de>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        jejb@...isc-linux.org, linux-parisc@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] parisc: DMA API: return error instead of BUG_ON for dma
 ops on non dma devs

On Wed, Jul 05, 2017 at 09:36:09PM +0200, Helge Deller wrote:
> On 05.07.2017 20:57, Christoph Hellwig wrote:
> > I've got a tree pending that removes DMA_ERROR_CODE, and it's been
> > in linux-next for a while.
> 
> I had the parisc patch in for-next as well and didn't received
> any warnings.

There are no warnings, as the macro just won't be used by common code
anymore.

But the commit is from July 3rd, and the pull request to Linus for
it was merged on the same day.  I can't see how it could have been
in linux-next for long.  It certainly wasn't in the last linux-next
release that I looked at before the long weekend (the July 30 one)

> Can we please change this to something like 
> "Prepare parisc to get rid of DMA_ERROR_CODE tree-wide" ?
> It's somewhat more neutral.

Fine with me.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ