From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Subject: Re: [PATCH] MAINTAINERS: add omap2plus_defconfig under OMAP SUPPORT
Date: Mon, 19 Jan 2015 14:05:09 -0800 [thread overview]
Message-ID: <20150119220508.GN18552@atomide.com> (raw)
In-Reply-To: <20150119215558.GW20386@saruman>
* Felipe Balbi <balbi@ti.com> [150119 13:59]:
> On Mon, Jan 19, 2015 at 10:52:56PM +0100, Javier Martinez Canillas wrote:
> > Hello Felipe,
> >
> > On Mon, Jan 19, 2015 at 10:45 PM, Felipe Balbi <balbi@ti.com> wrote:
> > > omap2plus_defconfig is also part of the OMAP Support
> > > maintained, because of that it's best to list it
> > > under OMAP SUPPORT on MAINTAINERS so people know
> > > to Cc linux-omap when patching that file.
> > >
> > > Reported-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
> > > Signed-off-by: Felipe Balbi <balbi@ti.com>
> > > ---
> > > MAINTAINERS | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 97de006f38f0..abc6281892e7 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -6783,6 +6783,7 @@ Q: http://patchwork.kernel.org/project/linux-omap/list/
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
> > > S: Maintained
> > > F: arch/arm/*omap*/
> > > +F: arch/arm/configs/omap2plus_defconfig
> >
> > While been there, could you please also add omap1_defconfig?
>
> Sure, Tony, is that ok ?
Oh yeah that would be nice :)
Tony
prev parent reply other threads:[~2015-01-19 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 21:45 [PATCH] MAINTAINERS: add omap2plus_defconfig under OMAP SUPPORT Felipe Balbi
2015-01-19 21:52 ` Javier Martinez Canillas
2015-01-19 21:55 ` Felipe Balbi
2015-01-19 22:05 ` Tony Lindgren [this message]
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=20150119220508.GN18552@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sjoerd.simons@collabora.co.uk \
/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).