From: Christoph Hellwig <hch@infradead.org>
To: Helge Deller <deller@gmx.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
jejb@parisc-linux.org, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: DMA API: return error instead of BUG_ON for dma ops on non dma devs
Date: Wed, 5 Jul 2017 13:33:35 -0700 [thread overview]
Message-ID: <20170705203335.GA10792@infradead.org> (raw)
In-Reply-To: <9de25038-5a0e-697d-dfb4-b6eb65189079@gmx.de>
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.
next prev parent reply other threads:[~2017-07-05 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 8:38 [PATCH] parisc: DMA API: return error instead of BUG_ON for dma ops on non dma devs Thomas Bogendoerfer
2017-07-03 14:41 ` Helge Deller
2017-07-05 18:57 ` Christoph Hellwig
2017-07-05 19:36 ` Helge Deller
2017-07-05 20:33 ` Christoph Hellwig [this message]
2017-07-05 20:51 ` Helge Deller
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=20170705203335.GA10792@infradead.org \
--to=hch@infradead.org \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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