linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Gustavo Silva <gustavograzs@gmail.com>
Cc: "Alex Lanzano" <lanzano.alex@gmail.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Lothar Rubusch" <l.rubusch@gmail.com>
Subject: Re: [PATCH v4 3/3] iio: imu: bmi270: add support for motion events
Date: Wed, 16 Jul 2025 12:49:28 +0300	[thread overview]
Message-ID: <aHd1qDR3jNTKBbun@smile.fi.intel.com> (raw)
In-Reply-To: <j7vqnxx3d6cws2zsveqohr6iqtno5thlauypnowlijifiwx5ow@6arfipnjkfh7>

On Tue, Jul 15, 2025 at 08:52:41PM -0300, Gustavo Silva wrote:
> On Tue, Jul 15, 2025 at 10:37:21AM +0300, Andy Shevchenko wrote:
> > On Fri, Jul 11, 2025 at 08:36:03PM -0300, Gustavo Silva wrote:

...

> > Is this already documented in ABI?
> > 
> Not yet. Should this have a device-specific ABI entry?

I don't know, but what I can say is that change is no-go without documented ABI.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-07-16  9:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250711-bmi270-events-v4-0-53ec7da35046@gmail.com>
2025-07-11 23:36 ` [PATCH v4 3/3] iio: imu: bmi270: add support for motion events Gustavo Silva
2025-07-15  7:37   ` Andy Shevchenko
2025-07-15  7:49     ` Andy Shevchenko
2025-07-15 23:55       ` Gustavo Silva
2025-07-16  9:53         ` Andy Shevchenko
2025-07-24 15:22           ` Jonathan Cameron
2025-07-24 21:26             ` Andy Shevchenko
2025-07-27 15:49               ` Jonathan Cameron
2025-08-02 11:58                 ` Jonathan Cameron
2025-08-04 22:26                   ` Gustavo Silva
2025-08-10 18:25                     ` Jonathan Cameron
2025-07-15 23:52     ` Gustavo Silva
2025-07-16  9:49       ` Andy Shevchenko [this message]
2025-07-24 15:28         ` Jonathan Cameron

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=aHd1qDR3jNTKBbun@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gustavograzs@gmail.com \
    --cc=jic23@kernel.org \
    --cc=l.rubusch@gmail.com \
    --cc=lanzano.alex@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /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;
as well as URLs for NNTP newsgroup(s).