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>
Subject: Re: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger
 allocate() stage
Thread-Topic: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger
 allocate() stage
Thread-Index: AQHYdd/Pt2zXEFx7c0Or/RCut5+rEK0/GLKAgCpM/oCAEyDEAIAErDEAgALhSACAAGbVgIABBkYA
Date:   Tue, 19 Jul 2022 09:11:33 +0000
Message-ID: <20220719091132.qfax7t2ogacur65u@CAB-WSD-L081021.sigma.sbrf.ru>
References: <20220601174837.20292-1-ddrokosov@sberdevices.ru>
 <20220604145955.2a1108ca@jic23-huawei>
 <20220701115823.vywhifktaxcr72cc@CAB-WSD-L081021.sigma.sbrf.ru>
 <20220713170436.32330fa6@jic23-huawei> <20220716162556.2e919bf7@jic23-huawei>
 <20220718112446.lucl7omialqri7yv@CAB-WSD-L081021.sigma.sbrf.ru>
 <20220718183249.6f411e5c@jic23-huawei>
In-Reply-To: <20220718183249.6f411e5c@jic23-huawei>
Accept-Language: ru-RU, en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CCB0717121BCD44BB0BFB8FC96D706E3@sberdevices.ru>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk

On Mon, Jul 18, 2022 at 06:32:49PM +0100, Jonathan Cameron wrote:
> On Mon, 18 Jul 2022 11:23:59 +0000
> Dmitry Rokosov <DDRokosov@sberdevices.ru> wrote:
>=20
> > Hello Jonathan,
> >=20
> > On Sat, Jul 16, 2022 at 04:25:56PM +0100, Jonathan Cameron wrote:
> > > On Wed, 13 Jul 2022 17:04:36 +0100
> > > Jonathan Cameron <jic23@kernel.org> wrote:
> > >  =20
> > > > On Fri, 1 Jul 2022 11:59:59 +0000
> > > > Dmitry Rokosov <DDRokosov@sberdevices.ru> wrote:
> > > >  =20
> > > > > Hello Jonathan,
> > > > >=20
> > > > > This patch has been on the mailing list for one month already, bu=
t no
> > > > > comments from other IIO reviewers. What do you think we should do=
 with it?
> > > > > Is it a helpful change or not?   =20
> > > >=20
> > > > Given I'm way behind and timing in cycle, I'm probably going to kic=
k this
> > > > back to start of the next cycle. Sorry for delay, =20
> > > Applied to the togreg branch of iio.git.
> > >=20
> > > I'm unlikely to do another pull request this cycle unless there is a =
delay in
> > > the release for some reason (and probably not even if there is), so t=
his
> > > is queued up for next cycle.  As such it'll sit exposed only in the t=
esting
> > > branch until I rebase on rc1.
> > >=20
> > > Thanks,
> > >=20
> > > Jonathan
> > >  =20
> >=20
> > Thank you for the patch applied.
> > I have one question about the previous already applied patchset
> >=20
> > https://lore.kernel.org/all/20220607183907.20017-1-ddrokosov@sberdevice=
s.ru/
> >=20
> > I see this patchset already merged to linux-next more than a month ago.
> > But it's still not available in the linux stable branch. Could you plea=
se
> > explain what's the problem with this one? Was some bug found during
> > linux-next testing stage? Should I fix something?
> >=20
> > Appreciate any help to understand what's I missing.
>=20
> It's not a fix so it will go in during the merge window in about 2 weeks =
time.
> Won't get backported to Stable though unless we ask for that to happen as=
 it's
> not really a fix so I didn't add a marking for it to be picked up for sta=
ble
> (which would only happen after 5.20-rc1 anyway).
>=20
> J

Thanks a lot for explanation!

--=20
Thank you,
Dmitry=