mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Doug Anderson <dianders@chromium.org>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	devicetree@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Cesar Eduardo Barros <cesarb@cesarb.net>,
	Joe Perches <joe@perches.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Don't send to devicetree list for "arch/*/boot/dts"
Date: Wed, 23 Oct 2013 23:54:48 +0100	[thread overview]
Message-ID: <20131023235448.4de21b8d.m.chehab@samsung.com> (raw)
In-Reply-To: <52680380.7020204@gmail.com>

Em Wed, 23 Oct 2013 12:12:32 -0500
Rob Herring <robherring2@gmail.com> escreveu:

> On 10/23/2013 08:22 AM, Doug Anderson wrote:
> > As discussed in the ARM kernel summit, people on the devicetree list
> > would no longer like to receive emails about all dts changes.  Remove
> > from MAINTAINERS.
> 
> We need to make sure platform maintainers are copied though. That may be
> hard since we don't have standard layout/naming of dts files.
> 
> We might also want to drop these:
> K:      of_get_property
> K:      of_match_table
> 
> They are at least on the wrong maintainer list now as they should be
> associated with the binding maintainers and not DT core code if we do
> keep them.
> 
> Also based on the discussion, we need to add
> Documentation/devicetree/bindings/* to appropriate subsystem
> maintainers, but that should probably wait until after Friday at least.

/me is confused. What's the procedure for the DT patches for the devices
supported by the subsystem I maintain, e. g. patches for
/drivers/media/platform? 

Should I just apply them, if I think that it is needed by the hardware? 
Are there any criteria to be followed? If so, what criteria?

/me hopes that all those questions will be discussed/answered at KS on
Friday's discussions ;)

In any case, my suggestion is that this patch should be a way more verbose,
and should come together with a patch adding something at Documentation
(SubmittingPatches, or maybe SubmitingDTPatches) in order to be sure that
both developers and subsystem maintainers will do the right thing.

Thanks,
Mauro
> 
> Rob
> 
> > 
> > Signed-off-by: Doug Anderson <dianders@chromium.org>
> > ---
> >  MAINTAINERS | 2 --
> >  1 file changed, 2 deletions(-)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ebaf8bd..0166e8e 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5987,7 +5987,6 @@ OMAP DEVICE TREE SUPPORT
> >  M:	Benoît Cousson <bcousson@baylibre.com>
> >  M:	Tony Lindgren <tony@atomide.com>
> >  L:	linux-omap@vger.kernel.org
> > -L:	devicetree@vger.kernel.org
> >  S:	Maintained
> >  F:	arch/arm/boot/dts/*omap*
> >  F:	arch/arm/boot/dts/*am3*
> > @@ -6167,7 +6166,6 @@ M:	Ian Campbell <ijc+devicetree@hellion.org.uk>
> >  L:	devicetree@vger.kernel.org
> >  S:	Maintained
> >  F:	Documentation/devicetree/
> > -F:	arch/*/boot/dts/
> >  F:	include/dt-bindings/
> >  
> >  OPENRISC ARCHITECTURE
> > 
> 


-- 

Cheers,
Mauro

  reply	other threads:[~2013-10-23 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 13:22 Doug Anderson
2013-10-23 17:12 ` Rob Herring
2013-10-23 22:54   ` Mauro Carvalho Chehab [this message]
2013-10-24 10:40     ` Rob Herring

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=20131023235448.4de21b8d.m.chehab@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=cesarb@cesarb.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=robherring2@gmail.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®