From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v8 1/1] gpio: add sloppy logic analyzer using polling
Date: Mon, 5 Jun 2023 08:31:07 +0200 [thread overview]
Message-ID: <ZH2BKzvk/1vS/tZE@shikoro> (raw)
In-Reply-To: <ZHjAF6xg1fAaJhQV@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
> Year passed. Any news here?
Well, the issue is that Steven Rostedt told me last years at Kernel
Recipes that disabling the RCU stall detector was bad. He gave me a
pointer where to look for a potentially better solution but I forgot to
note it. When I asked him by mail again for that pointer, he was too
busy to answer and since then I had other things to do. But Steve is at
EOSS end of June as well as me. Asking him again there is big on my
list. Nice you remembered this patch :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-05 6:31 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
2023-06-05 6:31 ` Wolfram Sang [this message]
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=ZH2BKzvk/1vS/tZE@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.