All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217
Date: Tue, 22 Dec 2015 11:31:52 -0800	[thread overview]
Message-ID: <20151222193152.GW30172@localhost> (raw)
In-Reply-To: <20151216134541.GA5574@afzalpc>

On Wed, Dec 16, 2015 at 07:15:41PM +0530, Afzal Mohammed wrote:
> Hi,
> 
> On Tue, Dec 15, 2015 at 08:49:07AM -0600, Nishanth Menon wrote:
> > On Tue, Dec 15, 2015 at 7:51 AM, Afzal Mohammed <afzal.mohd.ma@gmail.com> wrote:
> > > On Mon, Dec 14, 2015 at 12:42:58PM -0600, Nishanth Menon wrote:
> 
> > >> Enable PMIC for beaglebone similar to commit 7a5c6065669c ("ARM:
> > >> OMAP2+: omap2plus_defconfig: Add tps65217 support") - this allows
> > >> multi_v7_defconfig to boot up on older beaglebone platforms.
> > >
> > > A similar one -
> > >
> > > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/384289.html
> > >
> > > your v1 was earlier than the above, so mine should > /dev/null.
> > 
> > If you'd like to, please reply back on original patch dropping your
> > patch.. or if queued, I can drop mine (I dont see it on linux-next
> > yet).
> 
> That patch didn't get a reply at all, hence assuming that it won't be
> picked & don't want to create a noise on that silent thread ;), but if
> it gets applied, i will fight against my patch :)

As mentioned in the earlier reply, don't assume a patch that hasn't been
applied yet won't be -- please follow up with a redaction of it if that's what
you want. Since I go through my mail folder in chronological order, I come
across your patch first and will apply it when I get to it.

Anyway, not a big deal since the contents is the same.



-Olof

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: Nishanth Menon <nm@ti.com>, Russell King <linux@arm.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	ARM Linux <arm@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217
Date: Tue, 22 Dec 2015 11:31:52 -0800	[thread overview]
Message-ID: <20151222193152.GW30172@localhost> (raw)
In-Reply-To: <20151216134541.GA5574@afzalpc>

On Wed, Dec 16, 2015 at 07:15:41PM +0530, Afzal Mohammed wrote:
> Hi,
> 
> On Tue, Dec 15, 2015 at 08:49:07AM -0600, Nishanth Menon wrote:
> > On Tue, Dec 15, 2015 at 7:51 AM, Afzal Mohammed <afzal.mohd.ma@gmail.com> wrote:
> > > On Mon, Dec 14, 2015 at 12:42:58PM -0600, Nishanth Menon wrote:
> 
> > >> Enable PMIC for beaglebone similar to commit 7a5c6065669c ("ARM:
> > >> OMAP2+: omap2plus_defconfig: Add tps65217 support") - this allows
> > >> multi_v7_defconfig to boot up on older beaglebone platforms.
> > >
> > > A similar one -
> > >
> > > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/384289.html
> > >
> > > your v1 was earlier than the above, so mine should > /dev/null.
> > 
> > If you'd like to, please reply back on original patch dropping your
> > patch.. or if queued, I can drop mine (I dont see it on linux-next
> > yet).
> 
> That patch didn't get a reply at all, hence assuming that it won't be
> picked & don't want to create a noise on that silent thread ;), but if
> it gets applied, i will fight against my patch :)

As mentioned in the earlier reply, don't assume a patch that hasn't been
applied yet won't be -- please follow up with a redaction of it if that's what
you want. Since I go through my mail folder in chronological order, I come
across your patch first and will apply it when I get to it.

Anyway, not a big deal since the contents is the same.



-Olof

  parent reply	other threads:[~2015-12-22 19:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 18:42 [PATCH V2 0/3] ARM: multi_v7_defconfig: Enable more OMAP family platforms Nishanth Menon
2015-12-14 18:42 ` Nishanth Menon
2015-12-14 18:42 ` [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217 Nishanth Menon
2015-12-14 18:42   ` Nishanth Menon
2015-12-15 13:51   ` Afzal Mohammed
2015-12-15 13:51     ` Afzal Mohammed
2015-12-15 14:49     ` Nishanth Menon
2015-12-15 14:49       ` Nishanth Menon
2015-12-16 13:45       ` Afzal Mohammed
2015-12-16 13:45         ` Afzal Mohammed
2015-12-16 14:04         ` Nishanth Menon
2015-12-16 14:04           ` Nishanth Menon
2015-12-16 14:15           ` Afzal Mohammed
2015-12-16 14:15             ` Afzal Mohammed
2015-12-22 19:31         ` Olof Johansson [this message]
2015-12-22 19:31           ` Olof Johansson
2015-12-26 13:33           ` Afzal Mohammed
2015-12-26 13:33             ` Afzal Mohammed
2015-12-14 18:42 ` [PATCH V2 2/3] ARM: multi_v7_defconfig: Enable AM437x PMIC TPS65218 Nishanth Menon
2015-12-14 18:42   ` Nishanth Menon
2015-12-22 19:32   ` Olof Johansson
2015-12-22 19:32     ` Olof Johansson
2015-12-14 18:43 ` [PATCH V2 3/3] ARM: multi_v7_defconfig: Enable generic SoC internal OMAP regulators Nishanth Menon
2015-12-14 18:43   ` Nishanth Menon
2015-12-22 19:32   ` Olof Johansson
2015-12-22 19:32     ` Olof Johansson

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=20151222193152.GW30172@localhost \
    --to=olof@lixom.net \
    --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 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.