All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy@kernel.org>
To: Denis Benato <benato.denis96@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Alex Lanzano" <lanzano.alex@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Danila Tikhonov" <danila@jiaxyga.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"Derek J . Clark" <derekjohn.clark@gmail.com>,
	"Philip Müller" <philm@manjaro.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] iio: fix suspend and resume triggering for bmi160 and bmi270
Date: Mon, 26 May 2025 23:18:57 +0300	[thread overview]
Message-ID: <aDTMseDPCGoTRJR_@smile.fi.intel.com> (raw)
In-Reply-To: <86d1b019-faec-40ab-b850-8fad22dc4321@gmail.com>

On Mon, May 26, 2025 at 10:13:00PM +0200, Denis Benato wrote:
> On 5/26/25 21:58, Andy Shevchenko wrote:
> > On Sun, May 25, 2025 at 04:25:28PM +0200, Denis Benato wrote:
> >> Two imu devices bmi160 and bmi270 are similar to bmi323, with the same bug and
> >> a common usecase: fix the aforementioned bug about triggering not resuming
> >> after sleep in the same way it was solved for the bmi323 device driver.
> >>
> >> The bmi270 patch has been tested on a device where the device irq pin
> >> is connected to the CPU ensuring it doesn't cause harm to devices that
> >> do not use hrtimer or other external triggers.
> >>
> >> Changelog from v1 [1]
> >> - include linux/pm.h where needed
> >> - used "Closed" to reference the solved issue for each driver
> >> - merged two lines into one (on both drivers)
> > I got this series twice without any (?) difference in the versions. Care to
> > explain what's going on?
> >
> I am sorry: mails were not being sent to the main lkml nor the iio mailing list and so
> I resent to everybody, otherwise doing "answer to all" would have created a mess
> where discussions would get lost.

Always mention this kind of things in a cover letter when resending and
ideally add a word 'resend' to the Subject.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-05-26 20:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 14:25 [PATCH v2 0/2] iio: fix suspend and resume triggering for bmi160 and bmi270 Denis Benato
2025-05-25 14:25 ` [PATCH v2 1/2] iio: bmi270: suspend and resume triggering on relevant pm operations Denis Benato
2025-05-31 16:59   ` Jonathan Cameron
2025-05-25 14:25 ` [PATCH v2 2/2] iio: bmi160: " Denis Benato
2025-05-26 19:58 ` [PATCH v2 0/2] iio: fix suspend and resume triggering for bmi160 and bmi270 Andy Shevchenko
2025-05-26 20:13   ` Denis Benato
2025-05-26 20:18     ` Andy Shevchenko [this message]
2025-05-26 23:37       ` Denis Benato

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=aDTMseDPCGoTRJR_@smile.fi.intel.com \
    --to=andy@kernel.org \
    --cc=benato.denis96@gmail.com \
    --cc=danila@jiaxyga.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=lanzano.alex@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=peterz@infradead.org \
    --cc=philm@manjaro.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.