All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@wdc.com>
To: Paul Cercueil <paul@crapouillou.net>
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, 2 Aug 2020 13:42:51 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2008021339110.24175@redsun52.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <DGFFEQ.RMDW72DK0U5B1@crapouillou.net>

On Sun, 2 Aug 2020, Paul Cercueil wrote:

> >  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".

 Fair enough (and odd enough too to have two entries for one piece), 
though in this case I think the commit description ought to mention it.  
As it stands it makes one think the driver is not going to have a 
maintainer anymore: "[...] and no maintenance is provided."

  Maciej

  reply	other threads:[~2020-08-02 12:43 UTC|newest]

Thread overview: 10+ 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
2020-08-02 12:42     ` Maciej W. Rozycki [this message]
2020-08-02 16:46       ` Krzysztof Kozlowski
2020-08-17 18:41 Krzysztof Kozlowski
2020-08-17 18:41 ` Krzysztof Kozlowski
2020-09-11 15:38 ` 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=alpine.LFD.2.21.2008021339110.24175@redsun52.ssa.fujisawa.hgst.com \
    --to=macro@wdc.com \
    --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=paul@crapouillou.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.