public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	kernel <kernel@axis.com>, Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: buffer: Silence lock nesting splat
Date: Thu, 1 Sep 2022 09:04:23 +0200	[thread overview]
Message-ID: <YxBZd9Ivg5+zGUEb@axis.com> (raw)
In-Reply-To: <20220828163247.3d6417d9@jic23-huawei>

On Sun, Aug 28, 2022 at 05:32:47PM +0200, Jonathan Cameron wrote:
> Any plans to post updated roadtest soon?  I'm keen to add more test cases
> and use it to cleanup the remaining staging drivers.  Very helpful tool,
> but I don't want to be developing test sets against an old version if
> it's going to be costly to forward port it.

I don't think it's ready for a new posting, but I pushed the version I
currently have here:

 https://github.com/vwax/linux/commits/roadtest/devel

The tests only pass on v5.19 since there are a couple of regressions
(which affect real hardware too) in mainline:

 https://lore.kernel.org/all/a48011b9-a551-3547-34b6-98b10e7ff2eb@redhat.com/
 https://lore.kernel.org/all/YxBX4bXG02E4lSUW@axis.com/

  reply	other threads:[~2022-09-01  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16  8:08 [PATCH] iio: buffer: Silence lock nesting splat Vincent Whitchurch
2022-08-19  8:03 ` Andy Shevchenko
2022-08-20 11:08   ` Jonathan Cameron
2022-08-23  8:10     ` Vincent Whitchurch
2022-08-28 15:32       ` Jonathan Cameron
2022-09-01  7:04         ` Vincent Whitchurch [this message]
2022-08-20 11:06 ` Jonathan Cameron
2022-08-20 11:08   ` Lars-Peter Clausen
2022-08-23  8:12     ` Vincent Whitchurch

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=YxBZd9Ivg5+zGUEb@axis.com \
    --to=vincent.whitchurch@axis.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kernel@axis.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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