From: Christoph Hellwig <hch@lst.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 3/4] powerpc/powernv: remove dead NPU DMA code
Date: Wed, 19 Jun 2019 09:28:37 +0200 [thread overview]
Message-ID: <20190619072837.GA6858@lst.de> (raw)
In-Reply-To: <db502ec4-2e8f-fbc3-9db2-3fe98464a62c@ozlabs.ru>
On Wed, Jun 19, 2019 at 10:34:54AM +1000, Alexey Kardashevskiy wrote:
>
>
> On 23/05/2019 17:49, Christoph Hellwig wrote:
> > None of these routines were ever used since they were added to the
> > kernel.
>
>
> It is still being used exactly in the way as it was explained before in
> previous respins. Thanks.
Please point to the in-kernel user, because that is the only relevant
one. This is not just my opinion but we had a clear discussion on that
at least years kernel summit.
next prev parent reply other threads:[~2019-06-19 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 7:49 remove dead powernv code v2 Christoph Hellwig
2019-05-23 7:49 ` [PATCH 1/4] powerpc/powernv: remove the unused pnv_pci_set_p2p function Christoph Hellwig
2019-05-23 7:49 ` [PATCH 2/4] powerpc/powernv: remove the unused tunneling exports Christoph Hellwig
2019-06-21 1:47 ` Oliver O'Halloran
2019-06-21 9:21 ` Frederic Barrat
2019-06-21 9:24 ` Christoph Hellwig
2019-05-23 7:49 ` [PATCH 3/4] powerpc/powernv: remove dead NPU DMA code Christoph Hellwig
2019-06-19 0:34 ` Alexey Kardashevskiy
2019-06-19 7:28 ` Christoph Hellwig [this message]
2019-06-20 1:45 ` Alexey Kardashevskiy
2019-06-20 6:03 ` Christoph Hellwig
2019-06-20 6:20 ` Alexey Kardashevskiy
2019-06-20 6:21 ` Christoph Hellwig
2019-06-20 6:48 ` Alexey Kardashevskiy
2019-05-23 7:49 ` [PATCH 4/4] powerpc/powernv: remove the unused vas_win_paste_addr and vas_win_id functions Christoph Hellwig
2019-06-21 1:40 ` Oliver O'Halloran
2019-06-17 6:46 ` remove dead powernv code v2 Christoph Hellwig
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=20190619072837.GA6858@lst.de \
--to=hch@lst.de \
--cc=aik@ozlabs.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
/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).