public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-tegra@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: tegra: rebuild tegra_defconfig
Date: Tue, 28 May 2013 15:30:29 -0600	[thread overview]
Message-ID: <51A521F5.2010206@wwwdotorg.org> (raw)
In-Reply-To: <1369761972-31986-1-git-send-email-swarren@wwwdotorg.org>

On 05/28/2013 11:26 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
> 
> This simply rebuilds tegra_defconfig on top of next-20130520. As such, it
> should introduce no changes; simply moving entries around due to Kconfig
> ordering changes. The apparent exceptions are:
> 
> AUTO_ZRELADDR: Selected by ARM multi-platform support.
> MTD_CHAR: Removed in Kconfig.
> 
> This should make it easier to create future defconfig patches on top of
> linux-next, since all the extraneous diffs have been removed. It also
> makes it more likely that once 3.12 comes around, this defconfig will
> already match what's required there.

I've applied this (squashed it into) Tegra's for-3.11/defconfig branch.

  reply	other threads:[~2013-05-28 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 17:26 [PATCH] ARM: tegra: rebuild tegra_defconfig Stephen Warren
2013-05-28 21:30 ` Stephen Warren [this message]
     [not found]   ` <51A521F5.2010206-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-29 13:38     ` Marc Dietrich
     [not found]       ` <2234363.J239kID5LN-D3pzGp0ZKuDWZbiwp4sFPyrtisivX6KghOMvlBiLbJSELgA04lAiVw@public.gmane.org>
2013-05-29 15:29         ` Stephen Warren
     [not found]           ` <51A61EEC.5040300-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-29 17:30             ` Marc Dietrich
2013-05-29 17:42               ` Stephen Warren
  -- strict thread matches above, loose matches on Subject: below --
2014-06-16 18:04 Stephen Warren

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=51A521F5.2010206@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.com \
    /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