From: Rabin Vincent <rabin@rab.in>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linus.walleij@linaro.org, gnurou@gmail.com,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: add ETRAXFS GPIO driver
Date: Thu, 21 May 2015 21:09:33 +0200 [thread overview]
Message-ID: <20150521190933.GB6159@debian> (raw)
In-Reply-To: <1431784767.2341.28.camel@x220>
On Sat, May 16, 2015 at 03:59:27PM +0200, Paul Bolle wrote:
> On Sat, 2015-05-16 at 00:27 +0200, Rabin Vincent wrote:
> > +obj-$(CONFIG_GPIO_ETRAXFS) += gpio-etraxfs.o
>
> GPIO_ETRAXFS is a bool symbol, so gpio-etraxfs.o can only be built-in,
> right?
Right.
> > --- /dev/null
> > +++ b/drivers/gpio/gpio-etraxfs.c
>
> > +MODULE_DEVICE_TABLE(of, etraxfs_gpio_of_table);
>
> > +module_platform_driver(etraxfs_gpio_driver);
>
> (A patch was submitted that would allow built-in only code to use
> builtin_platform_driver(), see https://lkml.org/lkml/2015/5/10/125 .)
Thanks, good to know.
>
> > +MODULE_DESCRIPTION("ETRAX FS GPIO driver");
> > +MODULE_LICENSE("GPL");
>
> But the code this patch adds contains a bit of module specific
> boilerplate. Was it perhaps your intention to make GPIO_ETRAXFS
> tristate?
No, the intention is to have it boolean as it is now. I'll remove the
unnecessary lines.
next prev parent reply other threads:[~2015-05-21 19:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 22:27 [PATCH] gpio: add ETRAXFS GPIO driver Rabin Vincent
2015-05-16 13:59 ` Paul Bolle
2015-05-21 19:09 ` Rabin Vincent [this message]
2015-05-19 9:39 ` Linus Walleij
[not found] ` <CACRpkdZcbvrcOMJavU5TacR1nD5+ot2FdC5zxBc=8XdhZN0SqQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-21 18:48 ` Rabin Vincent
2015-05-21 18:48 ` Rabin Vincent
2015-06-01 13:45 ` Linus Walleij
2015-06-05 19:36 ` Rabin Vincent
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=20150521190933.GB6159@debian \
--to=rabin@rab.in \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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.