Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Dmitry Rokosov <DDRokosov@sberdevices.ru>
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
Date: Mon, 18 Jul 2022 18:32:49 +0100	[thread overview]
Message-ID: <20220718183249.6f411e5c@jic23-huawei> (raw)
In-Reply-To: <20220718112446.lucl7omialqri7yv@CAB-WSD-L081021.sigma.sbrf.ru>

On Mon, 18 Jul 2022 11:23:59 +0000
Dmitry Rokosov <DDRokosov@sberdevices.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@kernel.org> wrote:
> >   
> > > On Fri, 1 Jul 2022 11:59:59 +0000
> > > Dmitry Rokosov <DDRokosov@sberdevices.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


> 


  reply	other threads:[~2022-07-18 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 17:48 [RFC PATCH v1] iio: trigger: move trig->owner init to trigger allocate() stage Dmitry Rokosov
2022-06-04 13:59 ` Jonathan Cameron
2022-06-06 11:37   ` Dmitry Rokosov
2022-06-06 15:13     ` Jonathan Cameron
2022-07-01 11:59   ` Dmitry Rokosov
2022-07-13 16:04     ` Jonathan Cameron
2022-07-16 15:25       ` Jonathan Cameron
2022-07-18 11:23         ` Dmitry Rokosov
2022-07-18 17:32           ` Jonathan Cameron [this message]
2022-07-19  9:11             ` Dmitry Rokosov

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=20220718183249.6f411e5c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=DDRokosov@sberdevices.ru \
    --cc=andy.shevchenko@gmail.com \
    --cc=kernel@sberdevices.ru \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=robh+dt@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