mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-clk@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ML for reset controller sub-system?
Date: Mon, 02 Nov 2015 14:24:02 +0100	[thread overview]
Message-ID: <1446470642.3442.54.camel@pengutronix.de> (raw)
In-Reply-To: <CAK7LNARGbHqn9D3fDtN9xzwzFoYCur2qJUnnyRA4Q52D9XUVVA@mail.gmail.com>

Hi Masahiro,

Am Montag, den 02.11.2015, 22:05 +0900 schrieb Masahiro Yamada:
> Hi Philipp,
> 
> 
> I searched for the reset controller entry in MAINTAINERS.
> 
> 
> RESET CONTROLLER FRAMEWORK
> M:      Philipp Zabel <p.zabel@pengutronix.de>
> S:      Maintained
> F:      drivers/reset/
> F:      Documentation/devicetree/bindings/reset/
> F:      include/dt-bindings/reset/
> F:      include/linux/reset.h
> F:      include/linux/reset-controller.h
> 
> 
> Nothing is mentioned which mailing list
> reset controller patches should be sent to.
> 
> Please advise me.

There is no special reset-controller mailing list. Due to the low amount
of patches until now, I'm just using linux-kernel@vger.kernel.org.
scripts/get_maintainer.pl should give you the right list for existing
drivers.

For new drivers consider adding the SoC/architecture specific mailing
list to --cc, especially when coordination between reset and other
drivers is needed during bringup. If new device tree bindings are added,
always include devicetree@vger.kernel.org.

best regards
Philipp


  reply	other threads:[~2015-11-02 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 13:05 Masahiro Yamada
2015-11-02 13:24 ` Philipp Zabel [this message]
2015-11-02 16:05   ` Masahiro Yamada

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=1446470642.3442.54.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yamada.masahiro@socionext.com \
    /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

all inboxes | Powered by JetHome®