public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Brad Boyer <flar@allandria.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] nubus: Don't list card resources by default
Date: Sat, 25 Mar 2023 17:03:18 -0700	[thread overview]
Message-ID: <20230326000318.GB31801@allandria.com> (raw)
In-Reply-To: <CAMuHMdXi1mF=j_Qzzg971AqHF-JdgfaDd+v0HymXXusFt-WBUQ@mail.gmail.com>

On Sat, Mar 25, 2023 at 01:44:43PM +0100, Geert Uytterhoeven wrote:
> Perhaps it would be worthwhile to move the resources out of /proc,
> but into a separate virtual file system?
> That way people who need access to the additional info can load the
> separate virtual file system kernel module, and mount the file system?

I could be wrong, but I believe the more recent trend has been to
move things like this out of /proc anyway.

	Brad Boyer
	flar@allandria.com


  reply	other threads:[~2023-03-26  0:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  6:03 [PATCH v2] nubus: Don't list card resources by default Finn Thain
2023-03-23  8:19 ` Geert Uytterhoeven
2023-03-23 23:13   ` Finn Thain
2023-03-24  8:59     ` Brad Boyer
2023-03-24 23:35       ` Finn Thain
2023-03-25 12:44         ` Geert Uytterhoeven
2023-03-26  0:03           ` Brad Boyer [this message]
2023-03-26  8:23             ` Geert Uytterhoeven
2023-03-26  0:00         ` Brad Boyer
2023-03-26  3:22           ` Finn Thain
2023-03-23  8:39 ` Andreas Schwab
2023-03-23  8:41   ` Geert Uytterhoeven
2023-03-24  0:08     ` Finn Thain
2023-03-24  8:26       ` 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=20230326000318.GB31801@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox