From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>
Subject: linux-next: Fixes tag needs some work in the leds tree
Date: Wed, 22 Jul 2020 08:33:37 +1000 [thread overview]
Message-ID: <20200722083337.067e1445@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Hi all,
In commit
347b711870ab ("leds: multicolor: Fix camel case in documentation")
Fixes tag
Fixes: f5a6eb5c5e38 ("leds: multicolor: Introduce a multicolor class definition")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 59bb31e8549e ("leds: multicolor: Introduce a multicolor class definition")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-07-21 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 22:33 Stephen Rothwell [this message]
2020-07-22 13:15 ` linux-next: Fixes tag needs some work in the leds tree Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2019-08-25 21:19 Stephen Rothwell
2019-08-26 18:23 ` Jacek Anaszewski
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=20200722083337.067e1445@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmurphy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).