From: antoine.tenart@free-electrons.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: berlin: improve multi_v7_defconfig support
Date: Wed, 14 Oct 2015 15:09:35 +0200 [thread overview]
Message-ID: <20151014130935.GD20884@kwain> (raw)
In-Reply-To: <6303906.JnZ5PeFoqZ@wuerfel>
Hi Arnd,
On Wed, Oct 14, 2015 at 02:36:21PM +0200, Arnd Bergmann wrote:
> On Wednesday 14 October 2015 12:34:00 Antoine Tenart wrote:
> >
> > Some drivers used on a Marvell Berlin kernel were missing from
> > multi_v7_defconfig. This series add them.
>
> Adding them is great, but we try to have as much as possible
> in loadable modules for new additions. Can you do this?
Sure, I'll do this for the Ethernet and the ADC drivers. But we already
have the SATA and USB features built-in with multi_v7_defconfig, so I'll
keep the two PHY drivers built-in.
> Having a single patch instead of four different ones is fine too,
> by the way.
And I'll put them into a single patch.
Thanks,
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-14 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 10:34 [PATCH 0/4] ARM: berlin: improve multi_v7_defconfig support Antoine Tenart
2015-10-14 10:34 ` [PATCH 1/4] ARM: multi_v7_defconfig: enable Berlin SATA PHY Antoine Tenart
2015-10-14 10:34 ` [PATCH 2/4] ARM: multi_v7_defconfig: enable Berlin USB PHY Antoine Tenart
2015-10-14 10:34 ` [PATCH 3/4] ARM: multi_v7_defconfig: enable pxa168 Ethernet Antoine Tenart
2015-10-14 10:34 ` [PATCH 4/4] ARM: multi_v7_defconfig: enable the Berlin ADC Antoine Tenart
2015-10-14 12:36 ` [PATCH 0/4] ARM: berlin: improve multi_v7_defconfig support Arnd Bergmann
2015-10-14 13:09 ` Antoine Tenart [this message]
2015-10-14 13:23 ` 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=20151014130935.GD20884@kwain \
--to=antoine.tenart@free-electrons.com \
--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).