From: Alban <albeu@free.fr>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Aban Bedel <albeu@free.fr>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH 2/3] gpio: ath79: Move to the generic GPIO driver
Date: Sun, 1 Nov 2015 18:46:59 +0100 [thread overview]
Message-ID: <20151101184659.1824dc35@tock> (raw)
In-Reply-To: <CACRpkdY3Xjir7pHLhpT9nv1w-KA5E3a767vqZoQronyAWZ1F1w@mail.gmail.com>
On Sat, 31 Oct 2015 22:02:53 +0100
Linus Walleij <linus.walleij@linaro.org> wrote:
> On Fri, Oct 30, 2015 at 11:36 AM, Alban Bedel <albeu@free.fr> wrote:
>
> > Turn the ath79 driver into a true driver supporting multiple
> > instances while dropping most of the code in favor of the generic
> > MMIO GPIO driver.
> >
> > As the driver now depend on CONFIG_GPIO_GENERIC also add a Kconfig
> > entry to make the driver optional.
> >
> > Signed-off-by: Alban Bedel <albeu@free.fr>
>
> This patch looks nice but sadly does not apply to my "devel" branch in
> the GPIO tree:
> https://git.kernel.org/cgit/linux/kernel/git/linusw/linux-gpio.git/log/?h=devel
>
> Please rebase it on this branch or wait until after the merge window.
I see that you applied my previous patch "gpio: ath79: Convert to the
state container design pattern", this series was supposed to replace
this patch. I'm sorry I forgot to mention this. That old patch doesn't
make much sense any more as most of the code it changed just get
dropped in the move to GPIO_GENERIC.
> > +config GPIO_ATH79
> > + tristate "Atheros AR71XX/AR724X/AR913X GPIO support"
> > + default y if ATH79
> > + depends on ATH79 || COMPILE_TEST
>
> I think the build robot is complaining because of COMPILE_TEST. This
> driver doesn't really compile on anything else than ATH79 does it?
> Noone else has asm/mach-ath79/ar71xx_regs.h
>
> So I suggest dropping the compile test until this is fixed (e.g. by
> moving the GPIO register offsets into the driver, what do I know).
I'm going to split the compile test support to a separate patch.
Alban
next prev parent reply other threads:[~2015-11-01 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 10:36 [PATCH 1/3] MAINTAINERS: Add an entry for the ATH79 GPIO driver Alban Bedel
2015-10-30 10:36 ` [PATCH 2/3] gpio: ath79: Move to the generic " Alban Bedel
2015-10-30 11:42 ` kbuild test robot
2015-10-30 11:42 ` kbuild test robot
2015-10-31 21:02 ` Linus Walleij
2015-11-01 17:46 ` Alban [this message]
2015-11-02 8:30 ` Linus Walleij
2015-10-30 10:36 ` [PATCH 3/3] gpio: ath79: Make the driver removable Alban Bedel
2015-10-31 21:03 ` Linus Walleij
2015-10-31 20:56 ` [PATCH 1/3] MAINTAINERS: Add an entry for the ATH79 GPIO driver Linus Walleij
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=20151101184659.1824dc35@tock \
--to=albeu@free.fr \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.