From: Alexandre Courbot <acourbot@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: <linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<gnurou@gmail.com>, Alexandre Courbot <acourbot@nvidia.com>
Subject: [PATCH 0/3] Fixup patches for gpiod interface
Date: Sun, 20 Oct 2013 15:14:56 -0700 [thread overview]
Message-ID: <1382307299-22587-1-git-send-email-acourbot@nvidia.com> (raw)
These patches fix a few issues of the gpiod series highlighted by the
autobuild system. They take root in the fact that devres.c was compiled
even when gpiolib is not to be built, which should obviously not happen.
But they also reveal missing includes in the same file, and sparse also
pointed out a suspiscious line that happened to be completely wrong.
Patch 1/3 and 2/3 can be applied on their own, but would probably better
be squashed into bae48da2 "add gpiod_get() and gpiod_put() functions".
Patch 3/3 stands on its own, and should preferably be applied before the
rest of the gpiod series. It would not hurt to apply it after if 1/3 and
2/3 are properly squashed.
Apologies for these issues that could have been caught earlier had I been
less negligent.
Alexandre Courbot (3):
gpiolib: devres: fix devm_gpiod_get_index()
gpiolib: devres: add missing headers
gpiolib: make GPIO_DEVRES depend on GPIOLIB
drivers/gpio/Kconfig | 8 ++++----
drivers/gpio/devres.c | 4 +++-
2 files changed, 7 insertions(+), 5 deletions(-)
--
1.8.4.1
next reply other threads:[~2013-10-20 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 22:14 Alexandre Courbot [this message]
2013-10-20 22:14 ` [PATCH 1/3] gpiolib: devres: fix devm_gpiod_get_index() Alexandre Courbot
2013-10-23 8:09 ` Linus Walleij
2013-10-20 22:14 ` [PATCH 2/3] gpiolib: devres: add missing headers Alexandre Courbot
2013-10-20 22:14 ` [PATCH 3/3] gpiolib: make GPIO_DEVRES depend on GPIOLIB Alexandre Courbot
2013-10-23 8:13 ` Linus Walleij
2013-10-23 8:14 ` 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=1382307299-22587-1-git-send-email-acourbot@nvidia.com \
--to=acourbot@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®