From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: config: Add DLINK DIR665 options to multi_v5_defconfig
Date: Sun, 2 Nov 2014 13:41:11 -0800 [thread overview]
Message-ID: <20141102214111.GB17643@localhost> (raw)
In-Reply-To: <20141101234220.GN3698@titan.lakedaemon.net>
On Sat, Nov 01, 2014 at 07:42:20PM -0400, Jason Cooper wrote:
> arm-soc folks,
>
> On Fri, Oct 31, 2014 at 11:13:33PM +0100, Andrew Lunn wrote:
> > Enable building of the switch chip driver and the wireless driver
> > needed by the DLINK DIR665
> >
> > Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> > Cc: arm at kernel.org
> > ---
> > arch/arm/configs/multi_v5_defconfig | 2 ++
> > 1 file changed, 2 insertions(+)
>
> I went ahead and picked this since I don't foresee too many conflicts
> like there are with multi_v7_defconfig. Please let me know if you would
> prefer to take changes to this file directly.
Depends on if there's much other v5 activity this cycle or not. I don't think
there is a whole lot so you should be safe.
-Olof
next prev parent reply other threads:[~2014-11-02 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 22:13 [PATCH 0/4] Support for DLINK DIR665 Andrew Lunn
2014-10-31 22:13 ` [PATCH 1/4] ARM: Kirkwood: Add support for DLink DIR665 Andrew Lunn
2014-10-31 22:45 ` Claudio Leite
2014-11-01 16:03 ` Jason Cooper
2014-11-01 20:11 ` Andrew Lunn
2014-11-01 20:16 ` Jason Cooper
2014-10-31 22:13 ` [PATCH 2/4] ARM: Kirkwood: DIR665: Instantiate Distributed Switch Architecture Andrew Lunn
2014-10-31 22:13 ` [PATCH 3/4] ARM: mvebu: Add DLINK DIR665 options to mvebu_v5_defconfig Andrew Lunn
2014-10-31 22:13 ` [PATCH 4/4] ARM: config: Add DLINK DIR665 options to multi_v5_defconfig Andrew Lunn
2014-11-01 23:42 ` Jason Cooper
2014-11-02 21:41 ` Olof Johansson [this message]
2014-11-01 23:40 ` [PATCH 0/4] Support for DLINK DIR665 Jason Cooper
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=20141102214111.GB17643@localhost \
--to=olof@lixom.net \
--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).