mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Brad Boyer <flar@allandria.com>
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 08:50:59 +1000 (AEST)	[thread overview]
Message-ID: <e887a8c9-4310-a6cb-62d2-39db7d75d452@linux-m68k.org> (raw)
In-Reply-To: <20230403061827.GA3406@allandria.com>

On Sun, 2 Apr 2023, Brad Boyer wrote:

> On Sun, Mar 26, 2023 at 02:37:02PM +1100, Finn Thain wrote:
> > diff --git a/drivers/nubus/nubus.c b/drivers/nubus/nubus.c
> > index f70ba58dbc55..d2d2b580f646 100644
> > --- a/drivers/nubus/nubus.c
> > +++ b/drivers/nubus/nubus.c
> > @@ -32,6 +32,12 @@
> >  
> >  /* Globals */
> >  
> > +/* This parameter makes slot resources available in procfs. It's deprecated and
> > + * disabled by default as procfs is no longer thought to be suitable for that.
> > + */
> > +bool populate_procfs;
> > +module_param(populate_procfs, bool, 0);
> > +
> >  LIST_HEAD(nubus_func_rsrcs);
> >  
> >  /* Meaning of "bytelanes":
> 
> 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.

  reply	other threads:[~2023-04-03 22:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  3:37 Finn Thain
2023-04-03  6:18 ` Brad Boyer
2023-04-03 22:50   ` Finn Thain [this message]
2023-04-04 21:16     ` Brad Boyer

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=e887a8c9-4310-a6cb-62d2-39db7d75d452@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=flar@allandria.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®