From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/1] gpio: add sloppy logic analyzer using polling
Date: Wed, 22 Dec 2021 11:19:19 +0100 [thread overview]
Message-ID: <YcL7p5nzZs8vnojl@shikoro> (raw)
In-Reply-To: <CAMuHMdVh60ocfzkJKz8zR1hODr8SWp=sbyHrR3KGx2ntLmuFGQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
> Anyone with a clue? Thanks!
Yes, the search engines helped[1]. I run a minimal system, so when I
mount cpusets, it will actually mount cgroups with a default mount
option of "noprefix". But you likely run a rootfs with cgroups already,
so it gets mounted directly without "noprefix". Then, when the logic
analyzer tries to mount again, the implied default "noprefix" is
discarded.
[1] https://cgroups.vger.kernel.narkive.com/20fAhMNN/noprefix-mount-option
So, I will update the script to mount "cgroups" instead of "cpuset" and
use the newer filenames instead. This seems to be the proper way.
Thanks for testing, Geert!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-12-22 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 13:24 [PATCH v6 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2021-12-19 13:24 ` [PATCH v6 1/1] gpio: add sloppy " Wolfram Sang
2021-12-20 14:12 ` Geert Uytterhoeven
2021-12-20 20:01 ` Geert Uytterhoeven
2021-12-22 10:19 ` Wolfram Sang [this message]
2021-12-22 10:35 ` Geert Uytterhoeven
2021-12-22 12:58 ` Wolfram Sang
2022-01-07 17:08 ` Geert Uytterhoeven
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=YcL7p5nzZs8vnojl@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox