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 1/5] arm/defconfigs: Remove CONFIG_IPV6_PRIVACY
Date: Thu, 11 Aug 2016 23:51:38 +0200	[thread overview]
Message-ID: <1769762.X0BZWCkYAE@wuerfel> (raw)
In-Reply-To: <20160811213521.GD10636@nazgul.tnic>

On Thursday, August 11, 2016 11:35:21 PM CEST Borislav Petkov wrote:
> On Thu, Aug 11, 2016 at 10:26:26PM +0200, Arnd Bergmann wrote:
> > I'd prefer not to do it mechanically, please check the things that
> > changed to see if they made sense.
> 
> I'm hardly the guy to be in the position to verify ARM config stuff.
> Actually, my original intention was much simpler:
> 
> https://lkml.kernel.org/r/1459338168-29334-2-git-send-email-bp at alien8.de
> 
> but then Vladimir suggested I should do the savedefconfig thing.
> 

That patch looks good, sorry I missed it. I see that Vladimir already
did the lpc32xx portion of it, can you send the part for s3c24xx
to the exynos maintainers?

If you have larger chunks like CONFIG_INET_LRO removal, we can take
that directly through arm-soc as a single patch for all defconfigs.

	Arnd

  reply	other threads:[~2016-08-11 21:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1459338168-29334-1-git-send-email-bp@alien8.de>
2016-03-30 11:42 ` [PATCH 1/5] arm/defconfigs: Remove CONFIG_IPV6_PRIVACY Borislav Petkov
2016-04-20  9:59   ` Vladimir Zapolskiy
2016-08-11 17:00     ` Borislav Petkov
2016-08-11 20:26       ` Arnd Bergmann
2016-08-11 21:35         ` Borislav Petkov
2016-08-11 21:51           ` Arnd Bergmann [this message]
2016-08-12  5:22             ` Borislav Petkov
2016-08-12  6:19               ` Krzysztof Kozlowski

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=1769762.X0BZWCkYAE@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