linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Christian Brauner <brauner@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>, Zhangjin Wu <falcon@tinylab.org>,
	arnd@arndb.de, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	shuah@kernel.org
Subject: Re: [PATCH 0/2] proc: proc_setattr for /proc/$PID/net
Date: Thu, 13 Jul 2023 14:04:52 +0200	[thread overview]
Message-ID: <7a0d55f9-1cf9-4e30-bb20-2fee02af1515@t-8ch.de> (raw)
In-Reply-To: <20230713-walzwerk-flugaufnahme-680653f18f88@brauner>

On 2023-07-13 13:51:39+0200, Christian Brauner wrote:
> On Sun, Jul 09, 2023 at 07:10:58PM +0200, Thomas Weißschuh wrote:
> > Hi Willy,
> > 
> > On 2023-07-09 11:29:47+0200, Willy Tarreau wrote:
> > > On Fri, Jun 30, 2023 at 10:06:09PM +0800, Zhangjin Wu wrote:
> > >> [..]
> > > 
> > > Now queued, thanks!
> > > Willy
> > 
> > Don't we need an Ack from the fs maintainers for the patch to
> > fs/proc/proc_net.c ?
> > 
> > Personally I expected this series to go in via the fs tree because of
> > that patch.
> 
> I don't necessarily see patches I'm not Cced on.

Currently you are not listed explicitly maintainer for
"PROC FILESYSTEM" in MAINTAINERS.
If those should also go to you directly could you add yourself in
MAINTAINERS?
Otherwise get_maintainers.pl will miss your address.

Thomas

  reply	other threads:[~2023-07-13 12:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 10:30 [PATCH 0/2] proc: proc_setattr for /proc/$PID/net Thomas Weißschuh
2023-06-24 10:30 ` [PATCH 1/2] selftests/nolibc: drop test chmod_net Thomas Weißschuh
2023-06-24 10:30 ` [PATCH 2/2] proc: use generic setattr() for /proc/$PID/net Thomas Weißschuh
2023-07-13 11:49   ` Christian Brauner
2023-06-30 14:06 ` [PATCH 0/2] proc: proc_setattr " Zhangjin Wu
2023-07-09  9:29   ` Willy Tarreau
2023-07-09 17:10     ` Thomas Weißschuh
2023-07-09 17:27       ` Willy Tarreau
2023-07-09 17:57         ` Thomas Weißschuh
2023-07-09 18:04           ` Willy Tarreau
2023-07-09 18:22             ` Thomas Weißschuh
2023-07-10  7:09               ` Willy Tarreau
2023-07-10  7:36                 ` Thomas Weißschuh
2023-07-13 11:51       ` Christian Brauner
2023-07-13 12:04         ` Thomas Weißschuh [this message]
2023-07-13 11:58 ` Christian Brauner

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=7a0d55f9-1cf9-4e30-bb20-2fee02af1515@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=falcon@tinylab.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    /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;
as well as URLs for NNTP newsgroup(s).