From: Arnd Bergmann <arnd@arndb.de>
To: David Brown <davidb@codeaurora.org>
Cc: Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: msm: defconfigs for Qualcomm dev boards
Date: Tue, 30 Aug 2011 17:15:07 +0200 [thread overview]
Message-ID: <201108301715.07450.arnd@arndb.de> (raw)
In-Reply-To: <1314664573-18432-1-git-send-email-davidb@codeaurora.org>
On Tuesday 30 August 2011, David Brown wrote:
> Add default configs for the development boards for several Qualcomm
> MSM-family chips.
>
> Signed-off-by: David Brown <davidb@codeaurora.org>
> ---
> These are my current defconfigs for these targets. I'd like to get
> these into next so that the targets can get build tested. I'm not
> sure if we want to push them to mainline, since devicetree would
> theoretically eliminate the need for all of them.
I think it's reasonable to have them in mainline while the device
tree support on MSM is still incomplete, but I can also just
stick them in to a branch that I don't submit to mainline
if you prefer to have them only in linux-next.
Russell, if you want to keep the defconfig files under your
ownership, that's also fine with me. In that case:
Acked-by: Arnd Bergmann <arnd@arndb.de>
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: msm: defconfigs for Qualcomm dev boards
Date: Tue, 30 Aug 2011 17:15:07 +0200 [thread overview]
Message-ID: <201108301715.07450.arnd@arndb.de> (raw)
In-Reply-To: <1314664573-18432-1-git-send-email-davidb@codeaurora.org>
On Tuesday 30 August 2011, David Brown wrote:
> Add default configs for the development boards for several Qualcomm
> MSM-family chips.
>
> Signed-off-by: David Brown <davidb@codeaurora.org>
> ---
> These are my current defconfigs for these targets. I'd like to get
> these into next so that the targets can get build tested. I'm not
> sure if we want to push them to mainline, since devicetree would
> theoretically eliminate the need for all of them.
I think it's reasonable to have them in mainline while the device
tree support on MSM is still incomplete, but I can also just
stick them in to a branch that I don't submit to mainline
if you prefer to have them only in linux-next.
Russell, if you want to keep the defconfig files under your
ownership, that's also fine with me. In that case:
Acked-by: Arnd Bergmann <arnd@arndb.de>
Arnd
next prev parent reply other threads:[~2011-08-30 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 0:36 [PATCH] ARM: msm: defconfigs for Qualcomm dev boards David Brown
2011-08-30 0:36 ` David Brown
2011-08-30 15:15 ` Arnd Bergmann [this message]
2011-08-30 15:15 ` Arnd Bergmann
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=201108301715.07450.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.