From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Lee Jones <lee.jones@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andreas Kemnade <andreas@kemnade.info>
Subject: linux-next: Fixes tag needs some work in the mfd-fixes tree
Date: Fri, 5 Apr 2019 07:48:43 +1100 [thread overview]
Message-ID: <20190405074843.7f0013db@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
Hi Lee,
In commit
20bb907f7dc8 ("mfd: twl-core: Disable IRQ while suspended")
Fixes tag
Fixes: 6e2bd956936 ("i2c: omap: Use noirq system sleep pm ops to idle device for suspend")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: c6e2bd956936 ("i2c: omap: Use noirq system sleep pm ops to idle device for suspend")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-04-04 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 20:48 Stephen Rothwell [this message]
2019-04-04 21:21 ` linux-next: Fixes tag needs some work in the mfd-fixes tree Andreas Kemnade
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=20190405074843.7f0013db@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andreas@kemnade.info \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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