From: Arnd Bergmann <arnd@arndb.de>
To: Soren Brinkmann <soren.brinkmann@xilinx.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Olof Johansson <olof@lixom.net>,
Josh Cartwright <josh.cartwright@ni.com>,
Tony Prisk <linux@prisktech.co.nz>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 0/2] Extend multi_v7_defconfig
Date: Wed, 19 Jun 2013 20:46:40 +0200 [thread overview]
Message-ID: <201306192046.41005.arnd@arndb.de> (raw)
In-Reply-To: <1371664384-24974-1-git-send-email-soren.brinkmann@xilinx.com>
On Wednesday 19 June 2013, Soren Brinkmann wrote:
> I don't know how much a defconfig is supposed to provide, hence as RFC.
> This patches are needed for booting Zynq into a minimum ramfs based
> system with a serial console.
In my opinion we should provide enable all the platform specific drivers
in the defconfigs, as well as everything needed to boot the system,
to get proper compile coverage as well as the ability to test changes
easily. Your patches look good. Michal, would you apply them and
send another pull request or should I just take them directly?
Arnd
next prev parent reply other threads:[~2013-06-19 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 17:53 [PATCH RFC 0/2] Extend multi_v7_defconfig Soren Brinkmann
2013-06-19 17:53 ` [PATCH RFC 1/2] arm: multi_v7_defconfig: Enable Zynq UART driver Soren Brinkmann
2013-06-19 17:53 ` [PATCH RFC 2/2] arm: multi_v7_defconfig: Enable initrd/initramfs support Soren Brinkmann
2013-06-19 18:46 ` Arnd Bergmann [this message]
2013-06-20 5:23 ` [PATCH RFC 0/2] Extend multi_v7_defconfig Michal Simek
2013-06-20 8:02 ` Arnd Bergmann
2013-06-20 8:27 ` Michal Simek
2013-06-20 15:41 ` Sören Brinkmann
2013-06-20 15:56 ` Michal Simek
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=201306192046.41005.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=josh.cartwright@ni.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@prisktech.co.nz \
--cc=michal.simek@xilinx.com \
--cc=olof@lixom.net \
--cc=soren.brinkmann@xilinx.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