From: Michal Simek <monstr@monstr.eu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Soren Brinkmann <soren.brinkmann@xilinx.com>,
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: Thu, 20 Jun 2013 07:23:28 +0200 [thread overview]
Message-ID: <51C291D0.6000401@monstr.eu> (raw)
In-Reply-To: <201306192046.41005.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
On 06/19/2013 08:46 PM, Arnd Bergmann wrote:
> 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?
Soren asked me 2 days ago if make sense to create zynq defconfig or not.
I just suggested him to better extend this multi_v7_defconfig.
But still question is if we can/should create zynq specific defconfig?
Or are you going to remove all of these platform specific defconfig?
Definitely agree that multi_v7 defconfig should enable everything needed
to boot the system.
Does it also mean that we should also enable all zynq drivers
to get better compile coverage?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-06-20 5:23 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 ` [PATCH RFC 0/2] Extend multi_v7_defconfig Arnd Bergmann
2013-06-20 5:23 ` Michal Simek [this message]
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=51C291D0.6000401@monstr.eu \
--to=monstr@monstr.eu \
--cc=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;
as well as URLs for NNTP newsgroup(s).