Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Dmitry Rokosov <DDRokosov@sberdevices.ru>
To:     Jonathan Cameron <jic23@kernel.org>
CC:     "robh+dt@kernel.org" <robh+dt@kernel.org>,
        "lars@metafoo.de" <lars@metafoo.de>,
        "andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
        "noname.nuno@gmail.com" <noname.nuno@gmail.com>,
        "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
        kernel <kernel@sberdevices.ru>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "rockosov@gmail.com" <rockosov@gmail.com>
Subject: Re: [PATCH v3] iio: trigger: warn about non-registered iio trigger
 getting attempt
Thread-Topic: [PATCH v3] iio: trigger: warn about non-registered iio trigger
 getting attempt
Thread-Index: AQHYep3lZdCBX5wfLkWR1miHp7T4Oq1Rmw8AgANrnICABpNhAA==
Date:   Wed, 22 Jun 2022 17:51:56 +0000
Message-ID: <20220622175206.ddyyex7bezzh4rd4@CAB-WSD-L081021.sigma.sbrf.ru>
References: <20220607183907.20017-1-ddrokosov@sberdevices.ru>
 <20220616091308.miwqkdfc77mm72hz@CAB-WSD-L081021.sigma.sbrf.ru>
 <20220618142703.75025659@jic23-huawei>
In-Reply-To: <20220618142703.75025659@jic23-huawei>
Accept-Language: ru-RU, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BBC3AE6F80A9864EBADE94B6544763F9@sberdevices.ru>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk

Jonathan,

On Sat, Jun 18, 2022 at 02:27:03PM +0100, Jonathan Cameron wrote:
> On Thu, 16 Jun 2022 09:13:00 +0000
> Dmitry Rokosov <DDRokosov@sberdevices.ru> wrote:
>=20
> > Hello Jonathan,
> >=20
> > I notice the patchset from=20
> > https://lore.kernel.org/all/20220524181150.9240-1-ddrokosov@sberdevices=
.ru/
> > is not merged to stable yet.
> > I think if this WARN() patch is okay for you, maybe it's better to merg=
e
> > it together with the previous one. It will notify developers about this
> > problem as you suggested before, and the previous patchset resolves the=
 issue
> > in the all IIO drivers.
> >=20
> > What do you think about it?
>=20
> It would be a stretch to take a defensive measure like this into stable,
> so I'll just queue this up for the next merge window.  We might have
> some exciting intermediate times where anyone actually using the togreg
> branch directly will get drivers that will spit out the warning.
> That should only be people active on the list though who will find
> this quickly enough and understand what is gong on.
>=20
> I'm fine with this and it's been on list long enough for anyone else to c=
omment.
> It'll be in a branch I'm happy to rebase for at few days anyway if there
> are any last minute comments or tags.
>=20
> Applied to the togreg branch of iio.git and pushed out as testing.
>=20
> Hopefully I'll get a pull request out for the fixes-togreg branch
> sometime this weekend.

Thanks a lot for such detailed clarification! I'm seeing this warn
patchset in the linux-next already.

--=20
Thank you,
Dmitry=