From: Kent Gibson <warthog618@gmail.com>
To: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
bgolaszewski@baylibre.com, linus.walleij@linaro.org
Cc: Kent Gibson <warthog618@gmail.com>
Subject: [PATCH 0/2] gpiolib: cdev: fixes for split from gpiolib.c
Date: Fri, 12 Jun 2020 12:50:32 +0800 [thread overview]
Message-ID: <20200612045034.27425-1-warthog618@gmail.com> (raw)
A couple of minor fixes for the recent split from gpiolib.c:
The first fixes a couple of W=1 build warnings by including the module's
own header.
The second fixes the file comment. This was in v3 of the split patch,
but v2 got merged...
Kent Gibson (2):
gpiolib: cdev: fix -Wmissing-prototypes warnings
gpiolib: cdev: fix file comment
drivers/gpio/gpiolib-cdev.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
base-commit: f6d984418ffde19322fd149105200224ac2bc089
--
2.27.0
next reply other threads:[~2020-06-12 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 4:50 Kent Gibson [this message]
2020-06-12 4:50 ` [PATCH 1/2] gpiolib: cdev: fix -Wmissing-prototypes warnings Kent Gibson
2020-06-12 7:59 ` Bartosz Golaszewski
2020-06-12 4:50 ` [PATCH 2/2] gpiolib: cdev: fix file comment Kent Gibson
2020-06-12 8:00 ` Bartosz Golaszewski
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=20200612045034.27425-1-warthog618@gmail.com \
--to=warthog618@gmail.com \
--cc=bgolaszewski@baylibre.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