From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 0/2] gpio: mockup: minor maintenance
Date: Tue, 14 Jan 2020 16:02:51 +0100 [thread overview]
Message-ID: <20200114150253.28716-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Just two tweaks to the testing driver: update the license tag to conform
with the current SPDX list and sort the headers alphabetically for easier
maintenance.
Bartosz Golaszewski (2):
gpio: mockup: update the license tag
gpio: mockup: sort headers alphabetically
drivers/gpio/gpio-mockup.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
--
2.23.0
next reply other threads:[~2020-01-14 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 15:02 Bartosz Golaszewski [this message]
2020-01-14 15:02 ` [PATCH 1/2] gpio: mockup: update the license tag Bartosz Golaszewski
2020-01-14 15:02 ` [PATCH 2/2] gpio: mockup: sort headers alphabetically Bartosz Golaszewski
2020-01-15 10:28 ` [PATCH 0/2] gpio: mockup: minor maintenance 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=20200114150253.28716-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--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