Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "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
Subject: Re: [PATCH] iio: pressure: bmp280: drop sensor_data array
Date: Sat, 26 Apr 2025 16:27:01 +0100	[thread overview]
Message-ID: <20250426162701.4dd1f282@jic23-huawei> (raw)
In-Reply-To: <CAHp75VdAw8T_3t8=2JLO07zddjy1_eYX0bSoG9R=7TFPY9pWbA@mail.gmail.com>

On Wed, 23 Apr 2025 01:38:13 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Wed, Apr 23, 2025 at 1:32 AM David Lechner <dlechner@baylibre.com> wrote:
> > On 4/22/25 5:19 PM, Andy Shevchenko wrote:  
> > > On Wed, Apr 23, 2025 at 12:22 AM David Lechner <dlechner@baylibre.com> wrote:  
> 
> ...
> 
> > > Ah, I meant the plural: of the supported sensors. Otherwise are you
> > > talking only about one sensor?
> > >  
> > "each type of the sensors" doesn't sound right to me either.
> >
> > I am talking about more than one type, not more than one sensor. Sensor just
> > describes what types I am talking about.
> >
> > So perhaps we could just avoid it with "each different sensor type".  
> 
> Okay, it might be my misunderstanding... Use the original one if you
> think it's better.
> 

I stuck to original text.  Applied.

      reply	other threads:[~2025-04-26 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 19:28 [PATCH] iio: pressure: bmp280: drop sensor_data array David Lechner
2025-04-22 20:57 ` Andy Shevchenko
2025-04-22 21:22   ` David Lechner
2025-04-22 22:19     ` Andy Shevchenko
2025-04-22 22:32       ` David Lechner
2025-04-22 22:38         ` Andy Shevchenko
2025-04-26 15:27           ` Jonathan Cameron [this message]

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=20250426162701.4dd1f282@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.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