linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: afzal.mohd.ma@gmail.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217
Date: Tue, 15 Dec 2015 19:21:01 +0530	[thread overview]
Message-ID: <20151215135100.GA8288@afzalpc> (raw)
In-Reply-To: <1450118580-24754-2-git-send-email-nm@ti.com>

Hi,

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.

Seems Arnd wants multi_v7_defconfig changes thr' submaintainers rather
than directly (which I initially thought was supposed to be done)

Regards
afzal

  reply	other threads:[~2015-12-15 13:51 UTC|newest]

Thread overview: 13+ 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 ` [PATCH V2 1/3] ARM: multi_v7_defconfig: Enable beaglebone PMIC TPS65217 Nishanth Menon
2015-12-15 13:51   ` Afzal Mohammed [this message]
2015-12-15 14:49     ` Nishanth Menon
2015-12-16 13:45       ` Afzal Mohammed
2015-12-16 14:04         ` Nishanth Menon
2015-12-16 14:15           ` Afzal Mohammed
2015-12-22 19:31         ` Olof Johansson
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-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-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=20151215135100.GA8288@afzalpc \
    --to=afzal.mohd.ma@gmail.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).