From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [GIT PULL] gpio: fixes for v6.7-rc8
Date: Fri, 29 Dec 2023 20:42:09 +0100 [thread overview]
Message-ID: <20231229194209.13630-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Linus,
Here is a set of updates to the MAINTAINERS file, please pull for
the upcoming RC.
Thanks,
Bartosz Golaszewski
The following changes since commit 861deac3b092f37b2c5e6871732f3e11486f7082:
Linux 6.7-rc7 (2023-12-23 16:25:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.7-rc8
for you to fetch changes up to ad5575eb6278892aa25a5d249c5009860d6d8bbc:
MAINTAINERS: Add a missing file to the INTEL GPIO section (2023-12-27 15:55:44 +0100)
----------------------------------------------------------------
gpio fixes for v6.7-rc8
- Andy steps down as GPIO reviewer
- Kent becomes a reviewer for GPIO uAPI
- add missing intel file to the relevant MAINTAINERS section
----------------------------------------------------------------
Andy Shevchenko (2):
MAINTAINERS: Remove Andy from GPIO maintainers
MAINTAINERS: Add a missing file to the INTEL GPIO section
Bartosz Golaszewski (1):
MAINTAINERS: split out the uAPI into a new section
MAINTAINERS | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
next reply other threads:[~2023-12-29 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 19:42 Bartosz Golaszewski [this message]
2023-12-29 20:00 ` [GIT PULL] gpio: fixes for v6.7-rc8 pr-tracker-bot
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=20231229194209.13630-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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