From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3] nubus: Don't list slot resources by default
Date: Tue, 4 Apr 2023 14:16:18 -0700 [thread overview]
Message-ID: <20230404211618.GA26628@allandria.com> (raw)
In-Reply-To: <e887a8c9-4310-a6cb-62d2-39db7d75d452@linux-m68k.org>
On Tue, Apr 04, 2023 at 08:50:59AM +1000, Finn Thain wrote:
> On Sun, 2 Apr 2023, Brad Boyer wrote:
> > Would it be better to give this option a name that indicates that it is
> > for nubus only? These are effectively a global namespace. Other than
> > this, I don't see any issues.
>
> The name of the module here is "nubus", so this parameter is specified as
> "nubus.populate_procfs" in the kernel parameters. Without the "nubus" it
> doesn't work. I should probably add a comment about that.
OK. A comment would be good. Thank you for the clarification. It's been
a while since I needed to use anything like that myself. The code I
deal with on a regular basis is never built-in, so I missed how that
worked these days. Now that I looked at the headers, I see how that
works to add the prefix depending on the build type.
Brad Boyer
flar@allandria.com
prev parent reply other threads:[~2023-04-04 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 3:37 [RFC PATCH v3] nubus: Don't list slot resources by default Finn Thain
2023-04-03 6:18 ` Brad Boyer
2023-04-03 22:50 ` Finn Thain
2023-04-04 21:16 ` Brad Boyer [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=20230404211618.GA26628@allandria.com \
--to=flar@allandria.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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.