All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: MAINTAINERS entry for ARM/CLKDEV SUPPORT
Date: Mon, 10 Oct 2016 15:18:19 +0100	[thread overview]
Message-ID: <20161010141819.GA1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20161010140810.GA30609@mwanda>

On Mon, Oct 10, 2016 at 05:08:10PM +0300, Dan Carpenter wrote:
> Hello Stephen Boyd,

Okay, that's really not nice.

This is _not_ a question for Stephen.  Stephen does _not_ co-maintain
clkdev or the clk API, but co-maintains CCF.  I've no idea why you are
addressing this to Stephen when this is clearly a question for me to
answer.

> The MAINTAINERS entry looks like this:
> 
> ARM/CLKDEV SUPPORT
> M:      Russell King <linux@armlinux.org.uk>
> L:      linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> S:      Maintained
> F:      arch/arm/include/asm/clkdev.h
> F:      drivers/clk/clkdev.c
> 
> 
> We removed arch/arm/include/asm/clkdev.h in 34d2f4d3a4d6a6b ('ARM: Use
> generic clkdev.h header').  Do you still need to be CC'd on the clkdev.c
> changes?

Technically, it is redundant anyway, as I'm listed for all arch/arm
changes.  However, the maintainership of arch/arm and the maintainership
of clkdev are separate, the explicit entry is quite right.

It's also right that it's retained, because if we stop using the generic
clkdev.h header, I want to be copied on such a change, and this entry
will allow checkpatch to list me as clkdev maintainer.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-10-10 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 14:08 MAINTAINERS entry for ARM/CLKDEV SUPPORT Dan Carpenter
2016-10-10 14:18 ` Russell King - ARM Linux [this message]
2016-10-26 19:19   ` Dan Carpenter
2016-10-26 21:31     ` Stephen Boyd
2016-10-31 15:52       ` Russell King - ARM Linux

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=20161010141819.GA1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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 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.