From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Igor Putko <igorpetindev@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/3] gpio: tb10x: W=1 warning fix and style cleanups
Date: Fri, 26 Jun 2026 09:59:28 +0200 [thread overview]
Message-ID: <178246069892.6685.6018964536653587543.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260618155626.18751-1-igorpetindev@gmail.com>
On Thu, 18 Jun 2026 18:56:23 +0300, Igor Putko wrote:
> This series fixes a kernel-doc warning in the tb10x GPIO driver
> and addresses two minor checkpatch.pl coding style issues.
>
> Patch 1 fixes the kernel-doc structure formatting.
> Patch 2 replaces bare unsigned with unsigned int.
> Patch 3 removes unnecessary braces from a single-statement block.
>
> [...]
Applied, thanks!
[2/3] gpio: tb10x: use unsigned int instead of bare unsigned
https://git.kernel.org/brgl/c/23cf763ac5d084f9459a10a9fece9cb1ddc023d9
[3/3] gpio: tb10x: remove unnecessary braces
https://git.kernel.org/brgl/c/309f81de06c00c12a41e318633e1d1d0c9d67e2c
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
next prev parent reply other threads:[~2026-06-26 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 15:56 Igor Putko
2026-06-18 15:56 ` [PATCH 1/3] gpio: tb10x: fix struct tb10x_gpio kernel-doc Igor Putko
2026-06-18 15:56 ` [PATCH 2/3] gpio: tb10x: use unsigned int instead of bare unsigned Igor Putko
2026-06-18 15:56 ` [PATCH 3/3] gpio: tb10x: remove unnecessary braces Igor Putko
2026-06-22 8:14 ` (subset) [PATCH 0/3] gpio: tb10x: W=1 warning fix and style cleanups Bartosz Golaszewski
2026-06-26 7:59 ` Bartosz Golaszewski [this message]
2026-06-30 12:51 ` 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=178246069892.6685.6018964536653587543.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=igorpetindev@gmail.com \
--cc=linusw@kernel.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®