From: Alexandre Courbot <gnurou@gmail.com>
To: 陈华才 <chenhc@lemote.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
John Crispin <john@phrozen.org>,
"Steven J. Hill" <Steven.Hill@imgtec.com>,
linux-mips <linux-mips@linux-mips.org>,
Fuxin Zhang <zhangfx@lemote.com>,
wuzhangjin <wuzhangjin@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH V5 2/7] MIPS: Cleanup Loongson-2F's gpio driver
Date: Sat, 29 Nov 2014 00:03:41 +0900 [thread overview]
Message-ID: <CAAVeFuJZAxvVCpH0vQmYvF48F0XRoGNThFpDXjCPxQ_rrakHyg@mail.gmail.com> (raw)
In-Reply-To: <tencent_60EBDA3907E4C1985C37621B@qq.com>
On Fri, Nov 28, 2014 at 10:14 PM, 陈华才 <chenhc@lemote.com> wrote:
> I'm afraid that ARCH_HAVE_CUSTOM_GPIO_H cannot be simply removed, because ARCH_HAVE_CUSTOM_GPIO_H is slected by CONFIG_MIPS, other MIPS CPU (not Loongson) may need it.
Mmm, but all the custom gpio.h are in the mach- subdirectories, so
shouldn't this option be selected by each individual machine instead
of CONFIG_MIPS? If the MIPS maintainers agree with that, please add
one patch to do this change - otherwise just ignore my comment.
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-11-28 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 9:16 [PATCH V5 2/7] MIPS: Cleanup Loongson-2F's gpio driver Huacai Chen
2014-11-21 9:16 ` [PATCH V5 3/7] MIPS: Move Loongson GPIO driver to drivers/gpio Huacai Chen
2014-11-21 9:16 ` [PATCH V5 4/7] GPIO: Add Loongson-3A/3B GPIO driver support Huacai Chen
2014-11-28 7:48 ` [PATCH V5 2/7] MIPS: Cleanup Loongson-2F's gpio driver Alexandre Courbot
2014-11-28 13:14 ` 陈华才
2014-11-28 15:03 ` Alexandre Courbot [this message]
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=CAAVeFuJZAxvVCpH0vQmYvF48F0XRoGNThFpDXjCPxQ_rrakHyg@mail.gmail.com \
--to=gnurou@gmail.com \
--cc=Steven.Hill@imgtec.com \
--cc=chenhc@lemote.com \
--cc=john@phrozen.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.com \
/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).