The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Qingjie Xing <xqjcool@gmail.com>,
	christophe.jaillet@wanadoo.fr, willy@infradead.org,
	brauner@kernel.org, viro@zeniv.linux.org.uk,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] proc: Add a way to make proc files writable
Date: Fri, 1 Nov 2024 19:35:16 +0300	[thread overview]
Message-ID: <978cbbac-51ad-4f0b-8cb2-7a3807e6c98d@p183> (raw)
In-Reply-To: <20241031191453.a4c55e8b2bfb4bf8349f4287@linux-foundation.org>

On Thu, Oct 31, 2024 at 07:14:53PM -0700, Andrew Morton wrote:
> On Thu, 31 Oct 2024 18:39:20 -0700 Qingjie Xing <xqjcool@gmail.com> wrote:
> 
> > Provide an extra function, proc_create_single_write_data() that
> > act like its non-write version but also set a write method in
> > the proc_dir_entry struct. Alse provide a macro
> > proc_create_single_write to reduces the boilerplate code in the callers.
> > 
> 
> Please fully describe the reason for making this change.
> 
> Also, we are reluctant to add a new interface to Linux unless we add
> new users of that interface at the same time.

Yeah, /proc outside /proc/${pid} and /proc/sys should be pretty dead.

  reply	other threads:[~2024-11-01 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  1:39 [PATCH] proc: Add a way to make proc files writable Qingjie Xing
2024-11-01  2:14 ` Andrew Morton
2024-11-01 16:35   ` Alexey Dobriyan [this message]
2024-11-02  6:41     ` Qingjie Xing
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01  1:34 Qingjie Xing

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=978cbbac-51ad-4f0b-8cb2-7a3807e6c98d@p183 \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=xqjcool@gmail.com \
    /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