linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap: Run make savedefconfig on omap2plus_defconfig to shrink it
Date: Thu, 21 Apr 2011 10:53:03 +0200	[thread overview]
Message-ID: <20110421085303.GN31131@pengutronix.de> (raw)
In-Reply-To: <20110421084910.GF13688@atomide.com>

On Thu, Apr 21, 2011 at 01:49:10AM -0700, Tony Lindgren wrote:
> * Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> [110421 01:20]:
> > On Wed, Apr 20, 2011 at 11:44:23PM -0700, Tony Lindgren wrote:
> > > This shrinks it down a bit more and makes it easier
> > > to patch later on.
> > Maybe pointing out why it's shrinkable would be nice.
> > E.g.
> > 
> > 	After commit
> > 
> > 		ffb63e3 (omap2/3/4: Select all omaps and boards by default
> > 
> > 	many explicit settings can be dropped from the defconfig.
> 
> Good point, updated patch below.
> 
> Regards,
> 
> Tony
> 
> 
> From: Tony Lindgren <tony@atomide.com>
> Date: Wed, 20 Apr 2011 23:37:06 -0700
> Subject: [PATCH] omap: Run make savedefconfig on omap2plus_defconfig to shrink it
> 
> After commit ffb63e3 (omap2/3/4: Select all omaps and boards by default)
> may explicit settings can be dropped from the defconfig.
s/may/many/

I think ffb63e3 doesn't explain all changes, but ok.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2011-04-21  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  6:44 [PATCH] omap: Run make savedefconfig on omap2plus_defconfig to shrink it Tony Lindgren
2011-04-21  8:23 ` Uwe Kleine-König
2011-04-21  8:49   ` Tony Lindgren
2011-04-21  8:53     ` Uwe Kleine-König [this message]
2011-04-21  8:59       ` Tony Lindgren

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=20110421085303.GN31131@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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).