linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v8 1/1] gpio: add sloppy logic analyzer using polling
Date: Thu, 1 Jun 2023 18:59:18 +0300	[thread overview]
Message-ID: <ZHjAVnDAM/YzZSem@smile.fi.intel.com> (raw)
In-Reply-To: <ZHjAF6xg1fAaJhQV@smile.fi.intel.com>

On Thu, Jun 01, 2023 at 06:58:15PM +0300, Andy Shevchenko wrote:
> On Wed, May 25, 2022 at 05:07:39PM +0200, Wolfram Sang wrote:
> > On Wed, Mar 30, 2022 at 05:51:10PM +0300, Andy Shevchenko wrote:
> > > On Tue, Mar 29, 2022 at 11:11:26AM +0200, Wolfram Sang wrote:
> > > > This is a sloppy logic analyzer using GPIOs. It comes with a script to
> > > > isolate a CPU for polling. While this is definitely not a production
> > > > level analyzer, it can be a helpful first view when remote debugging.
> > > > Read the documentation for details.
> > > 
> > > Good enough I think,
> > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > 
> > Thanks, Andy!
> > 
> > To GPIO maintainers: can we apply the "new-driver-rule" and still have
> > it in 5.19? There can't be any regression and it has all comments
> > addressed. Also, I am talking about this project at Kernel Recipes late
> > next week and it would be great to say that it is finally merged :)
> 
> Year passed. Any news here?

Ah, GPIO maintainers probably missed this since no Cc.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2023-06-01 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  9:11 [PATCH v8 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2022-03-29  9:11 ` [PATCH v8 1/1] gpio: add sloppy " Wolfram Sang
2022-03-30 14:51   ` Andy Shevchenko
2022-05-25 15:07     ` Wolfram Sang
2023-06-01 15:58       ` Andy Shevchenko
2023-06-01 15:59         ` Andy Shevchenko [this message]
2023-06-05  6:31         ` Wolfram Sang
2023-06-01 21:39   ` andy.shevchenko
2023-06-02  6:51     ` Geert Uytterhoeven
2023-06-02  6:57       ` Geert Uytterhoeven
2023-06-02 14:07         ` Andy Shevchenko
2023-06-02  7:40       ` Greg KH

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=ZHjAVnDAM/YzZSem@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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).