From: Christoph Hellwig <hch@lst.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Christoph Hellwig <hch@lst.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Oliver O'Halloran <oohall@gmail.com>,
Frederic Barrat <fbarrat@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 3/4] powerpc/powernv: remove unused NPU DMA code
Date: Thu, 27 Jun 2019 09:22:40 +0200 [thread overview]
Message-ID: <20190627072240.GA9916@lst.de> (raw)
In-Reply-To: <027a5095-a22c-2799-8ff6-42d0bc4d2bc9@ozlabs.ru>
On Thu, Jun 27, 2019 at 10:21:55AM +1000, Alexey Kardashevskiy wrote:
> > Which comment? Last time I asked you complaint "it is still used in
> > exactly the same way as before" which you later clarified that you
> > have a hidden out of tree user somewhere, and you only objected to
>
> It is not hidden, anyone can download and inspect that GPL driver.
For one no one has ever posted a link. And second as mentioned
countless times it doesn't matter, it only matters if it is in mainline,
or as a special exception actively trying to go mainline.
> > the word "dead". That has been fixed and there were no further
> > comments.
>
> You still have it in the cover letter so at very least 3/4 is not a part
> of this patchset then.
>
> And I still want to see a formal statement about out-of-tree drivers
> support/tolerance. If you manage to remove this code, I'll have to post
> a revert (again and again) but I would rather know the exact list of
> what we do and what we do not do about such drivers and if the list 1)
> exists 2) is reasonable then I could try to come up with a better
> solution or point others to the policy and push them to do the right
> thing. Right now it is just you pretending that the nVidia driver does
> not exist, this is not helping. Thanks,
We had that discussion at kernel summit and it was reported. Anyway,
adding Greg, who usually has some pretty good prewritten letters for
this kind of thing.
next prev parent reply other threads:[~2019-06-27 7:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 14:52 remove unused powernv code v3 Christoph Hellwig
2019-06-25 14:52 ` [PATCH 1/4] powerpc/powernv: remove the unused pnv_pci_set_p2p function Christoph Hellwig
2019-07-03 14:27 ` Michael Ellerman
2019-07-03 14:33 ` Christoph Hellwig
2019-06-25 14:52 ` [PATCH 2/4] powerpc/powernv: remove the unused tunneling exports Christoph Hellwig
2019-06-25 14:52 ` [PATCH 3/4] powerpc/powernv: remove unused NPU DMA code Christoph Hellwig
2019-06-26 0:44 ` Alexey Kardashevskiy
2019-06-26 7:49 ` Christoph Hellwig
2019-06-27 0:21 ` Alexey Kardashevskiy
2019-06-27 7:22 ` Christoph Hellwig [this message]
2019-06-27 16:51 ` Greg Kroah-Hartman
2019-06-25 14:52 ` [PATCH 4/4] powerpc/powernv: remove the unused vas_win_paste_addr and vas_win_id functions Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-06-25 8:15 remove unused powernv code v2 Christoph Hellwig
2019-06-25 8:15 ` [PATCH 3/4] powerpc/powernv: remove unused NPU DMA code 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=20190627072240.GA9916@lst.de \
--to=hch@lst.de \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--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).