All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] regulator: axp20x: Fix LDO4 linear voltage range
Date: Wed, 27 Apr 2016 11:32:28 +0100	[thread overview]
Message-ID: <20160427103228.GI3217@sirena.org.uk> (raw)
In-Reply-To: <f63acd04-33ed-02d6-0ce4-b9c436a3bf84@redhat.com>

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

On Wed, Apr 27, 2016 at 11:46:29AM +0200, Hans de Goede wrote:
> On 26-04-16 16:57, Mark Brown wrote:

> >I have no record of any such patch, I don't know where it might've been
> >sent.

> It is here:

Please follow the normal submission workflow, don't pick random new
places to send things.  It's fine to copy extra places but if you don't
send to the normal places your patches are likely to not be seen.

> https://groups.google.com/forum/#!topic/linux-sunxi/3sjt47-CtbU

That's linux-sunxi and linux-arm-kernel but not linux-kernel where
regulator patches are supposed to be sent.  I did go look to see if I
could see anything on lkml but there was nothing visible from you.

> And according to that archive it was send to broonie@linaro.org
> (amongst others).

That's my work address, not broonie@kernel.org which is the address I
use consistently and which is what is advertised in MAINTAINERS.  That
goes somewhere completely different which isn't set up to handle patches
and since essentialy everything that does manage to get sent there is
also sent to the right place things sent there tend to get deleted
unread when I'm doing inbox triage which I imagine is what happened
here.  This is the one that's most critical.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: axp20x: Fix LDO4 linear voltage range
Date: Wed, 27 Apr 2016 11:32:28 +0100	[thread overview]
Message-ID: <20160427103228.GI3217@sirena.org.uk> (raw)
In-Reply-To: <f63acd04-33ed-02d6-0ce4-b9c436a3bf84@redhat.com>

On Wed, Apr 27, 2016 at 11:46:29AM +0200, Hans de Goede wrote:
> On 26-04-16 16:57, Mark Brown wrote:

> >I have no record of any such patch, I don't know where it might've been
> >sent.

> It is here:

Please follow the normal submission workflow, don't pick random new
places to send things.  It's fine to copy extra places but if you don't
send to the normal places your patches are likely to not be seen.

> https://groups.google.com/forum/#!topic/linux-sunxi/3sjt47-CtbU

That's linux-sunxi and linux-arm-kernel but not linux-kernel where
regulator patches are supposed to be sent.  I did go look to see if I
could see anything on lkml but there was nothing visible from you.

> And according to that archive it was send to broonie at linaro.org
> (amongst others).

That's my work address, not broonie at kernel.org which is the address I
use consistently and which is what is advertised in MAINTAINERS.  That
goes somewhere completely different which isn't set up to handle patches
and since essentialy everything that does manage to get sent there is
also sent to the right place things sent there tend to get deleted
unread when I'm doing inbox triage which I imagine is what happened
here.  This is the one that's most critical.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160427/8e8d939d/attachment.sig>

  reply	other threads:[~2016-04-27 10:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 14:00 [PATCH] regulator: axp20x: Fix LDO4 linear voltage range Maxime Ripard
2016-04-26 14:00 ` Maxime Ripard
2016-04-26 14:18 ` Chen-Yu Tsai
2016-04-26 14:18   ` Chen-Yu Tsai
2016-04-26 14:57   ` Mark Brown
2016-04-26 14:57     ` Mark Brown
2016-04-27  9:46     ` Hans de Goede
2016-04-27  9:46       ` Hans de Goede
2016-04-27 10:32       ` Mark Brown [this message]
2016-04-27 10:32         ` Mark Brown
2016-04-26 18:25 ` Applied "regulator: axp20x: Fix LDO4 linear voltage range" to the regulator tree Mark Brown
2016-04-26 18:25   ` Mark Brown

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=20160427103228.GI3217@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.