From: Paul Cercueil <paul@crapouillou.net>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH v2 1/2] MAINTAINERS: Remove JZ4780 DMA driver entry
Date: Sun, 02 Aug 2020 09:57:49 +0200 [thread overview]
Message-ID: <DGFFEQ.RMDW72DK0U5B1@crapouillou.net> (raw)
In-Reply-To: <alpine.LFD.2.21.2008012327070.24175@redsun52.ssa.fujisawa.hgst.com>
Hi Maciej,
Le sam. 1 août 2020 à 23:30, Maciej W. Rozycki <macro@wdc.com> a
écrit :
> On Sun, 26 Jul 2020, Krzysztof Kozlowski wrote:
>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index cba0ed77775b..362863cae239 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8541,11 +8541,6 @@ F: include/uapi/rdma/
>> F: samples/bpf/ibumad_kern.c
>> F: samples/bpf/ibumad_user.c
>>
>> -INGENIC JZ4780 DMA Driver
>> -M: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>
>> -S: Maintained
>> -F: drivers/dma/dma-jz4780.c
>> -
>
> FYI, the usual approach would be marking the entry "Orphan" rather
> than
> removing it entirely, so that the mapping remains and makes it easy
> for
> someone to pick it up.
This is OK in this case, as the driver is also listed as part of the
"INGENIC JZ47xx SoCs".
-Paul
next prev parent reply other threads:[~2020-08-02 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 15:55 [PATCH v2 1/2] MAINTAINERS: Remove JZ4780 DMA driver entry Krzysztof Kozlowski
2020-07-26 15:55 ` [PATCH v2 2/2] MAINTAINERS: Add linux-mips mailing list to JZ47xx entries Krzysztof Kozlowski
2020-08-01 22:30 ` [PATCH v2 1/2] MAINTAINERS: Remove JZ4780 DMA driver entry Maciej W. Rozycki
2020-08-02 7:57 ` Paul Cercueil [this message]
2020-08-02 12:42 ` Maciej W. Rozycki
2020-08-02 16:46 ` Krzysztof Kozlowski
2020-08-17 18:41 Krzysztof Kozlowski
2020-09-11 15:38 ` Krzysztof Kozlowski
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=DGFFEQ.RMDW72DK0U5B1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=macro@wdc.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).