From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: enable useful configurations for Vybrid
Date: Fri, 26 Feb 2016 17:23:45 +0100 [thread overview]
Message-ID: <3925334.GbIll3VaQm@wuerfel> (raw)
In-Reply-To: <1455156652-6950-1-git-send-email-stefan@agner.ch>
On Wednesday 10 February 2016 18:10:52 Stefan Agner wrote:
> Enable configuration options useful for Vybrid:
> - NFC NAND driver
> - USB dual-role controller (and Chipidea Gadget support)
> - Built-in EDMA DMA driver (to be available at LPUART probe)
> - Vybrid ADC driver
> - IIO hwmon support (used in i.MX 23/28, patch pending for Vybrid)
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
>
I've applied this to the next/defconfig branch in arm-soc directly now.
I think it wasn't completely clear what should happen to this when Olof
picked up all other patches and pull requests. I'd recommend to send
patches like this one through the normal platform maintainers instead,
or if that doesn't work make sure that arm at kernel.org is on the
recipient list.
Arnd
prev parent reply other threads:[~2016-02-26 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 2:10 [PATCH] ARM: multi_v7_defconfig: enable useful configurations for Vybrid Stefan Agner
2016-02-26 16:23 ` Arnd Bergmann [this message]
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=3925334.GbIll3VaQm@wuerfel \
--to=arnd@arndb.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