From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Jia Wang <wangjia@ultrarisc.com>,
linux-gpio@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] pinctrl: Export pinctrl_get_group_selector()
Date: Mon, 15 Jun 2026 14:49:41 +0200 [thread overview]
Message-ID: <ai_0i2cicHHzwIXj@monoceros> (raw)
In-Reply-To: <CAD++jLm+rv+Tm-WxvD51ynKeDUrPMAG=nfTNxRbf8FvSNy+dGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Mon, Jun 15, 2026 at 02:27:59PM +0200, Linus Walleij wrote:
> On Mon, Jun 15, 2026 at 12:16 PM Uwe Kleine-König
> <u.kleine-koenig@baylibre.com> wrote:
> > Checkpatch criticises:
> >
> > WARNING: Reported-by: should be immediately followed by Closes: or Link: with a URL to the report
> > #9:
> > Reported-by: Nathan Chancellor <nathan@kernel.org>
> > Reported-by: kernel test robot <lkp@intel.com>
>
> Now that is just checkpatch being silly, because what in in next looks
> like this:
>
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202606130210.ytVPxHlm-lkp@intel.com/
> Fixes: cb7037924836 ("pinctrl: ultrarisc: Add UltraRISC DP1000
> pinctrl driver")
> Signed-off-by: Linus Walleij <linusw@kernel.org>
Yeah, so the kernel test robot report has a Closes, but Nathan's
doesn't.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-15 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-13 20:02 [PATCH] pinctrl: Export pinctrl_get_group_selector() Linus Walleij
2026-06-15 10:16 ` Uwe Kleine-König
2026-06-15 12:27 ` Linus Walleij
2026-06-15 12:49 ` Uwe Kleine-König [this message]
2026-06-15 13:01 ` 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=ai_0i2cicHHzwIXj@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=wangjia@ultrarisc.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.