From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Bartosz Golaszewski <brgl@bgdev•pl>
Cc: Kent Gibson <warthog618@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tags need some work in the gpio-brgl-fixes tree
Date: Mon, 18 Jan 2021 08:21:09 +1100 [thread overview]
Message-ID: <20210118082109.725aff1a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Hi all,
In commit
ec6c3364b816 ("tools: gpio: fix %llu warning in gpio-watch.c")
Fixes tag
Fixes: commit 33f0c47b8fb4 ("tools: gpio: implement gpio-watch")
has these problem(s):
- leading word 'commit' unexpected
In commit
56835f1c14bc ("tools: gpio: fix %llu warning in gpio-event-mon.c")
Fixes tag
Fixes: commit 03fd11b03362 ("tools/gpio/gpio-event-mon: fix warning")
has these problem(s):
- leading word 'commit' unexpected
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-01-17 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 21:21 Stephen Rothwell [this message]
2021-01-17 23:48 ` linux-next: Fixes tags need some work in the gpio-brgl-fixes tree Kent Gibson
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=20210118082109.725aff1a@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brgl@bgdev$(echo .)pl \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=warthog618@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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