public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: multi_v5_defconfig: Enable recommended options for systemd
Date: Mon, 18 Apr 2016 21:28:35 +0200	[thread overview]
Message-ID: <5243175.i5zkJhBvDK@wuerfel> (raw)
In-Reply-To: <20160412142654.GA24304@tiger>

On Tuesday 12 April 2016 22:26:54 Shawn Guo wrote:
> On Tue, Apr 12, 2016 at 01:57:48PM +0200, Jan L?bbe wrote:
> > On Sa, 2016-03-26 at 12:28 +0100, Jan Luebbe wrote:
> > > Enable FHANDLE, CGROUPS, BLK_DEV_BSG and DEVTMPFS as recommended by
> > > systemd (which also matches the multi_v7 defconfig). Also enable IPV6,
> > > which defaults to 'y' by now.
> > > 
> > > Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
> > 
> > Shawn, you've already applied 1/2. Do you have any concerns or comments
> > regarding this one?
> 
> I thought that Arnd's request and Sascha's ACK only applies to 1/2.
> Just applied 2/2 as well.  @Arnd, let me know if I shouldn't.
> 
> 

I'd like to see both get picked up into the same branch if the changes are
for the same platform, sorry if that wasn't clear enough.

I guess in this case you can argue that the actual changes of 2/2 are
not imx specific at all, and I'd be fine with picking them up directly,
but I tend to prefer the defconfig changes to come from one of the subarch
maintainers just so I don't have to watch too carefully for patches
on the mailing list.

	Arnd

  reply	other threads:[~2016-04-18 19:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 11:28 [PATCH 1/2] ARM: multi_v5_defconfig: Enable support for MX21/MX27 Jan Luebbe
2016-03-26 11:28 ` [PATCH 2/2] ARM: multi_v5_defconfig: Enable recommended options for systemd Jan Luebbe
2016-04-12 11:57   ` Jan Lübbe
2016-04-12 14:26     ` Shawn Guo
2016-04-18 19:28       ` Arnd Bergmann [this message]
2016-03-29 22:28 ` [PATCH 1/2] ARM: multi_v5_defconfig: Enable support for MX21/MX27 Arnd Bergmann
2016-04-01 11:53 ` Sascha Hauer
2016-04-06 14:44   ` Shawn Guo

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=5243175.i5zkJhBvDK@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