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/4] ARM: mach-s5p: get rid of all <mach/gpio.h> headers
Date: Fri, 06 Jun 2014 08:50:04 +0200	[thread overview]
Message-ID: <4393612.d5qsoYg5L1@wuerfel> (raw)
In-Reply-To: <4544212.mqY6dSouMv@wuerfel>

On Wednesday 04 June 2014 15:58:28 Arnd Bergmann wrote:
> On Wednesday 04 June 2014 15:33:56 Linus Walleij wrote:
> > This renames all the local <mach/gpio.h> headers in the S5P platforms
> > to <mach/gpio-samsung.h> indicating a scope local to this platform,
> > and cuts the implicit inclusion of <mach/gpio.h> from <linux/gpio.h>
> > by removing the use of NEED_MACH_GPIO_H from all S5P variants.
> > 
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > 
> 
> Hmm, this patch will obviously clash with the removal of S5p64xx
> and s5pc100. It shouldn't be hard to resolve the conflict when we
> merge both into arm-soc/next/cleanup, but maybe there is a way to
> avoid it?

Nevermind, given how happy everyone is to see this gone, let's go
ahead with your current version, and let us handle the conflict in
arm-soc when we merge both patch sets.

	Arnd

  reply	other threads:[~2014-06-06  6:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 13:33 [PATCH 0/4] <mach/gpio.h> purge Linus Walleij
2014-06-04 13:33 ` [PATCH 1/4] ARM: s5p: cut the custom ARCH_NR_GPIOS definition Linus Walleij
2014-06-04 13:33 ` [PATCH 2/4] ARM: mach-s5p: get rid of all <mach/gpio.h> headers Linus Walleij
2014-06-04 13:58   ` Arnd Bergmann
2014-06-06  6:50     ` Arnd Bergmann [this message]
2014-06-09 11:36     ` Linus Walleij
2014-06-09 12:11       ` Arnd Bergmann
2014-06-04 13:33 ` [PATCH 3/4] ARM: kill CONFIG_NEED_MACH_GPIO_H Linus Walleij
2014-06-04 13:33 ` [PATCH 4/4] ARM: delete old reference to ARM_GPIOLIB_COMPLEX Linus Walleij
2014-06-04 17:23 ` [PATCH 0/4] <mach/gpio.h> purge Rob Herring
2014-06-06  5:10 ` Alexandre Courbot

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=4393612.d5qsoYg5L1@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