From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver
Date: Wed, 06 Jul 2016 17:43:44 -0700 [thread overview]
Message-ID: <1467852224.8360.60.camel@perches.com> (raw)
In-Reply-To: <CACgAJHyvusvRPKNaxHLFK=gWw2UUtjV80H175eRu6EieutxNiw@mail.gmail.com>
On Wed, 2016-07-06 at 17:35 -0700, Tai Tri Nguyen wrote:
> Hi Joe,
Ch?o Tai.
> On Wed, Jul 6, 2016 at 5:19 PM, Joe Perches <joe@perches.com> wrote:
> > On Wed, 2016-07-06 at 17:07 -0700, Tai Nguyen wrote:
[]
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > []
> > >
> > > @@ -8593,6 +8593,14 @@ L:?????linux-scsi at vger.kernel.org
> > > ?S:???Supported
> > > ?F:???drivers/scsi/pm8001/
> > >
> > > +PMU-XGENE
> > > +APPLIED MICRO (APM) X-GENE SOC PMU
> > One line section header please.
> Is this strictly required?
Yes.
get_maintainer.pl doesn't like multiple line section headers.
next prev parent reply other threads:[~2016-07-07 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 0:07 [PATCH v7 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-07-07 0:07 ` [PATCH v7 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver Tai Nguyen
2016-07-07 0:19 ` Joe Perches
2016-07-07 0:35 ` Tai Tri Nguyen
2016-07-07 0:43 ` Joe Perches [this message]
2016-07-07 1:01 ` Tai Tri Nguyen
2016-07-07 0:07 ` [PATCH v7 2/4] Documentation: Add documentation for APM X-Gene SoC PMU DTS binding Tai Nguyen
2016-07-07 0:07 ` [PATCH v7 3/4] perf: xgene: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-07-10 0:00 ` Paul Gortmaker
2016-07-11 18:12 ` Tai Tri Nguyen
2016-07-11 11:39 ` Mark Rutland
2016-07-11 16:47 ` Tai Tri Nguyen
2016-07-07 0:07 ` [PATCH v7 4/4] arm64: dts: apm: Add APM X-Gene SoC PMU DTS entries Tai Nguyen
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=1467852224.8360.60.camel@perches.com \
--to=joe@perches.com \
--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 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).