public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: akpm@linux-foundation.org, Laxman Dewangan <ldewangan@nvidia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] Fix up a pointer-integer size mismatch warning in tps62360_probe()
Date: Mon, 6 Jan 2014 17:00:28 +0000	[thread overview]
Message-ID: <20140106170028.GJ31886@sirena.org.uk> (raw)
In-Reply-To: <13465.1389026428@warthog.procyon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

On Mon, Jan 06, 2014 at 04:40:28PM +0000, David Howells wrote:
> Mark Brown <broonie@kernel.org> wrote:

> > you need to CC things to maintainers

> 	warthog>grep -i tps6 MAINTAINERS 
> 	warthog1>

> I cc'd Laxman who is the only person mentioned in the file.

> I cc'd you who is mentioned in the "regulator" section and who appears in
> sign-offs in the log.

But you didn't CC Liam who comaintains the subsystem and for me you used
a random address from signoffs on old commits (which you will doubtless
have noticed bounces) rather than the address in MAINTAINERS.  It looks
awfully like you only used signoffs here...

> There is no "regulator" list in the MAINTAINERS file.

Right, lkml is fine there - IIRC that was prompted by another patch I
noticed in the series, or it could just have been part of the
boilerplate response for these things.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-01-06 17:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 16:07 [PATCH 5/7] Fix up a pointer-integer size mismatch warning in tps62360_probe() David Howells
2014-01-06 12:42 ` Mark Brown
2014-01-06 16:40   ` David Howells
2014-01-06 17:00     ` Mark Brown [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=20140106170028.GJ31886@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.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