[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220718183249.6f411e5c@jic23-huawei>
Date: Mon, 18 Jul 2022 18:32:49 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Dmitry Rokosov <DDRokosov@...rdevices.ru>
Cc: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"lars@...afoo.de" <lars@...afoo.de>,
"andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
"noname.nuno@...il.com" <noname.nuno@...il.com>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
kernel <kernel@...rdevices.ru>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger
allocate() stage
On Mon, 18 Jul 2022 11:23:59 +0000
Dmitry Rokosov <DDRokosov@...rdevices.ru> wrote:
> Hello Jonathan,
>
> 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@...nel.org> wrote:
> >
> > > On Fri, 1 Jul 2022 11:59:59 +0000
> > > Dmitry Rokosov <DDRokosov@...rdevices.ru> wrote:
> > >
> > > > Hello Jonathan,
> > > >
> > > > This patch has been on the mailing list for one month already, but no
> > > > comments from other IIO reviewers. What do you think we should do with it?
> > > > Is it a helpful change or not?
> > >
> > > Given I'm way behind and timing in cycle, I'm probably going to kick this
> > > back to start of the next cycle. Sorry for delay,
> > Applied to the togreg branch of iio.git.
> >
> > 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 this
> > is queued up for next cycle. As such it'll sit exposed only in the testing
> > branch until I rebase on rc1.
> >
> > Thanks,
> >
> > Jonathan
> >
>
> Thank you for the patch applied.
> I have one question about the previous already applied patchset
>
> https://lore.kernel.org/all/20220607183907.20017-1-ddrokosov@sberdevices.ru/
>
> 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 please
> explain what's the problem with this one? Was some bug found during
> linux-next testing stage? Should I fix something?
>
> Appreciate any help to understand what's I missing.
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 stable
(which would only happen after 5.20-rc1 anyway).
J
>
Powered by blists - more mailing lists