Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andrej Valek <andrej.v@skyrain.eu>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Puranjay Mohan <puranjay@kernel.org>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	David Lechner <dlechner@baylibre.com>,
	Kessler Markus <markus.kessler@hilti.com>
Subject: Re: [PATCH v4] iio: accel: fix ADXL355 startup race condition
Date: Mon, 20 Oct 2025 19:00:32 +0100	[thread overview]
Message-ID: <20251020190032.0deb54a4@jic23-huawei> (raw)
In-Reply-To: <6ced29c5-bca2-4c29-beb4-b566f4d9bf17@skyrain.eu>

On Sun, 19 Oct 2025 12:45:27 +0200
Andrej Valek <andrej.v@skyrain.eu> wrote:

> Hello Jonathan,
> 
> On 18.10.2025 15:08, Jonathan Cameron wrote:
> > On Tue, 14 Oct 2025 09:13:44 +0200
> > Andrej Valek <andrej.v@skyrain.eu> wrote:
> >  
> >> From: Valek Andrej <andrej.v@skyrain.eu>
> >>
> >> There is an race-condition where device is not full working after SW reset.
> >> Therefore it's necessary to wait some time after reset and verify shadow
> >> registers values by reading and comparing the values before/after reset.
> >> This mechanism is described in datasheet at least from revision D.
> >>
> >> Fixes: 12ed27863ea3 ("iio: accel: Add driver support for ADXL355")
> >> Signed-off-by: Valek Andrej <andrej.v@skyrain.eu>
> >> Signed-off-by: Kessler Markus <markus.kessler@hilti.com>  
> > It doesn't hugely matter but I was only asking for a reply with the single
> > line David sent. Not a new posting of the driver.  
> Ah ok, I misunderstood it then.
> >
> > Definitely don't ever send two v4 with any changes at all as that makes
> > it uncertain what automation will pick up.  Standard b4 string to grab this
> > patch grabs me two patches with two patches as it can't figure out they are
> > the same.  
> Sorry about that.
> >
> > Anyhow, applied carefully by hand to get just this one and marked for
> > stable inclusion.
> >
> > Thanks,
> >
> > Jonathan
> >  
> Ok, good to know and thanks for the guiding. Will try to do it better in 
> the future.
> 
> Btw, you swapped my name and surname again, at least in the commit 
> (author) :).

I'm confused.  Your
From: Valek Andrej <andrej.v@skyrain.eu>
line is at at the top of the patch.

If you have one of those it will ignore whatever email address the mail came from.
https://lore.kernel.org/all/20251014071344.151914-1-andrej.v@skyrain.eu/

So I think this is a git config issue your end if you'd prefer it listed as
Andrej Valek.

Jonathan

> 
> BR,
> Andy


      reply	other threads:[~2025-10-20 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06  9:58 [PATCH v4] iio: accel: fix ADXL355 startup race condition Andrej Valek
2025-10-12 15:26 ` Jonathan Cameron
2025-10-13  7:07   ` Andrej Valek
2025-10-13 14:51     ` David Lechner
2025-10-14  7:13 ` Andrej Valek
2025-10-18 13:08   ` Jonathan Cameron
2025-10-19 10:45     ` Andrej Valek
2025-10-20 18:00       ` 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=20251020190032.0deb54a4@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andrej.v@skyrain.eu \
    --cc=dlechner@baylibre.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=markus.kessler@hilti.com \
    --cc=puranjay@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