From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: RE: linux-next: Fixes tag needs some work in the staging.current tree
Date: Fri, 11 Oct 2019 08:10:23 +0000 [thread overview]
Message-ID: <53418B0A3A5CEF439F1108674285B0A903FE8CC8@lhreml523-mbs.china.huawei.com> (raw)
In-Reply-To: <20191011074242.3d78c336@canb.auug.org.au>
Hi Stephen
Sorry, I've clearly let another one of these through.
Stupid question of the day. Don't suppose you can share how you check these?
Thanks,
Jonathan
-----Original Message-----
From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
Sent: 10 October 2019 21:43
To: Greg KH <greg@kroah.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Lorenzo Bianconi <lorenzo@kernel.org>; Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: linux-next: Fixes tag needs some work in the staging.current tree
Hi all,
In commit
85ae3aeedecc ("iio: imu: st_lsm6dsx: forbid 0 sensor sensitivity")
Fixes tag
Fixes: c8d4066c7246 ("iio: imu: st_lsm6dsx: remove invalid gain value for LSM9DS1")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: 0f7e17286b45 ("iio: imu: st_lsm6dsx: remove invalid gain value for LSM9DS1")
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2019-10-11 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 20:42 linux-next: Fixes tag needs some work in the staging.current tree Stephen Rothwell
2019-10-11 8:10 ` Jonathan Cameron [this message]
2019-10-11 8:29 ` Greg KH
2019-10-11 10:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2019-07-28 13:01 Stephen Rothwell
2019-07-28 13:13 ` Greg KH
2019-07-29 8:24 ` Jonathan Cameron
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=53418B0A3A5CEF439F1108674285B0A903FE8CC8@lhreml523-mbs.china.huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=sfr@canb.auug.org.au \
/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.