All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Defconfig update for LPC32xx
Date: Thu, 19 Apr 2012 19:12:53 +0200	[thread overview]
Message-ID: <4F904795.4050505@antcom.de> (raw)

Hi,

I'm planning to update arch/arm/configs/lpc32xx_defconfig, adjusting to
device tree and new driver options.

Now I wonder if I should (1) just add drivers which are used on the
reference machine (PHYTEC LPC3250 board) or (2) additionally add all
drivers that I have seen together with LPC32xx on other boards also,
which would demonstrate that the same binary kernel runs on all LPC32xx
machines, but increasing kernel size a bit.

I would prefer option (2) but first want to ask for advice.

Thanks in advance,

Roland

WARNING: multiple messages have this Message-ID (diff)
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: Defconfig update for LPC32xx
Date: Thu, 19 Apr 2012 19:12:53 +0200	[thread overview]
Message-ID: <4F904795.4050505@antcom.de> (raw)

Hi,

I'm planning to update arch/arm/configs/lpc32xx_defconfig, adjusting to
device tree and new driver options.

Now I wonder if I should (1) just add drivers which are used on the
reference machine (PHYTEC LPC3250 board) or (2) additionally add all
drivers that I have seen together with LPC32xx on other boards also,
which would demonstrate that the same binary kernel runs on all LPC32xx
machines, but increasing kernel size a bit.

I would prefer option (2) but first want to ask for advice.

Thanks in advance,

Roland

             reply	other threads:[~2012-04-19 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 17:12 Roland Stigge [this message]
2012-04-19 17:12 ` Defconfig update for LPC32xx Roland Stigge
2012-04-20 14:54 ` Arnd Bergmann
2012-04-20 14:54   ` 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=4F904795.4050505@antcom.de \
    --to=stigge@antcom.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.