From: Sasha Levin <Alexander.Levin@microsoft.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Song Qiang <songqiang1304521@gmail.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"lars@metafoo.de" <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v6 1/2] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.
Date: Fri, 21 Sep 2018 14:56:54 +0000 [thread overview]
Message-ID: <20180921145651.GS3821@sasha-vm> (raw)
In-Reply-To: <20180920094139.000065fe@huawei.com>
On Thu, Sep 20, 2018 at 09:41:39AM +0100, Jonathan Cameron wrote:
>On Wed, 19 Sep 2018 18:58:37 +0000
>Sasha Levin <Alexander.Levin@microsoft.com> wrote:
>
>> Hi,
>>
>> [This is an automated email]
>>
>> This commit has been processed because it contains a -stable tag.
>> The stable tag indicates that it's relevant for the following trees: all
>>
>> The bot has tested the following trees: v4.18.8, v4.14.70, v4.9.127, v4.=
4.156, v3.18.122,
>>
>> v4.18.8: Build OK!
>> v4.14.70: Failed to apply! Possible dependencies:
>> 22aac3eb0c46 ("MAINTAINERS: add entry for STM32 I2C driver")
>>
>> v4.9.127: Failed to apply! Possible dependencies:
>> 22aac3eb0c46 ("MAINTAINERS: add entry for STM32 I2C driver")
>> 78f839029e1d ("iio: distance: srf08: add IIO driver for us ranger")
>>
>> v4.4.156: Failed to apply! Possible dependencies:
>> 22aac3eb0c46 ("MAINTAINERS: add entry for STM32 I2C driver")
>> 78f839029e1d ("iio: distance: srf08: add IIO driver for us ranger")
>>
>> v3.18.122: Failed to apply! Possible dependencies:
>> 22aac3eb0c46 ("MAINTAINERS: add entry for STM32 I2C driver")
>> 4193c0f1d863 ("iio: driver for Semtech SX9500 proximity solution")
>> 78f839029e1d ("iio: distance: srf08: add IIO driver for us ranger")
>>
>>
>> Please let us know how to resolve this.
>>
>> --
>> Thanks,
>> Sasha
>Hi Sasha,
>
>This is a false detection. The stable tag is in the context of the
>additions to MAINTAINERS. I guess that is a rare enough case it's not
>worth fixing in your scripts, but thought I'd point it out incase you
>want to do so!
Hah, interesting!
I'll get it fixed, thanks!=
next prev parent reply other threads:[~2018-09-21 20:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 8:24 [PATCH v6 1/2] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor Song Qiang
2018-09-18 8:24 ` [PATCH v6 2/2] iio: proximity: vl53l0x: add interrupt support Song Qiang
2018-09-22 15:05 ` Jonathan Cameron
2018-09-26 22:46 ` Rob Herring
2018-09-28 9:36 ` Song Qiang
2018-09-28 23:52 ` Rob Herring
2018-09-29 11:10 ` Jonathan Cameron
2018-09-29 23:49 ` Rob Herring
2018-09-30 15:20 ` Jonathan Cameron
2018-10-01 3:58 ` Song Qiang
2018-10-01 18:44 ` Jonathan Cameron
2018-09-19 18:58 ` [PATCH v6 1/2] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor Sasha Levin
2018-09-20 8:41 ` Jonathan Cameron
2018-09-21 14:56 ` Sasha Levin [this message]
2018-09-22 14:46 ` Jonathan Cameron
2018-09-22 14:56 ` Himanshu Jha
2018-09-22 15:12 ` Jonathan Cameron
2018-09-22 15:28 ` Song Qiang
2018-09-22 15:44 ` 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=20180921145651.GS3821@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=songqiang1304521@gmail.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).