Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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.12-rc5
Date: Fri, 25 Oct 2024 16:25:04 +0200	[thread overview]
Message-ID: <20241025142504.44267-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Linus,

Please pull the following MAINTAINERS update that adds a keyword pattern
to the GPIO entry the goal of which is to alert us to anyone trying to
use the deprecated, legacy API (this happens almost every release).

Thanks,
Bartosz

The following changes since commit 8e929cb546ee42c9a61d24fae60605e9e3192354:

  Linux 6.12-rc3 (2024-10-13 14:33:32 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git tags/gpio-fixes-for-v6.12-rc5

for you to fetch changes up to 7e336a6c15ec7675adc1b376ca176ab013642098:

  MAINTAINERS: add a keyword entry for the GPIO subsystem (2024-10-22 09:13:10 +0200)

----------------------------------------------------------------
gpio fixes for v6.12-rc5

- update MAINTAINERS with a keyword pattern for legacy GPIO API

----------------------------------------------------------------
Bartosz Golaszewski (1):
      MAINTAINERS: add a keyword entry for the GPIO subsystem

 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2024-10-25 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 14:25 Bartosz Golaszewski [this message]
2024-10-25 18:10 ` [GIT PULL] gpio fixes for v6.12-rc5 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=20241025142504.44267-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --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