public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: WangYuli <wangyuli@uniontech.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Kent Overstreet <kent.overstreet@linux.dev>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write
Date: Wed, 25 Dec 2024 17:00:17 +0100	[thread overview]
Message-ID: <20241225160017.GA10283@1wt.eu> (raw)
In-Reply-To: <D7FF3455CE14824B+a3218eef-f2b6-4a9b-8daf-1d54c533da50@uniontech.com>

On Wed, Dec 25, 2024 at 11:42:29PM +0800, WangYuli wrote:
> On 2024/12/25 21:30, Andy Shevchenko wrote:
> 
> > Don't you think the Cc list is a bit overloaded?
> 
> Hi,
> 
> I apologize for any inconvenience this may cause.
> 
> I understand that under normal circumstances, one would simply pass the
> modified code path as an argument to the kernel's scripts/get_maintainer.pl
> script to determine the appropriate recipients.
> 
> However, given the vast and complex nature of the Linux kernel community,
> with tens of thousands of developers worldwide, and considering the varying
> "customs" of different subsystems, as well as time zone differences and
> individual work habits, it's not uncommon for patches to be sent to mailing
> lists and subsequently ignored or left pending.
(...)

Sorry, but by CCing 191 random addresses like this, that's the best way
to be added to .procmailrc and be completely ignored by everyone. At some
point one should wonder whether that's a common practice or if such
behaviors will be considered offensive by the majority. get_maintainer.pl
only lists the 2 lists and 3 addresses I left in CC (after Kent and Andy
whom I left since they replied to you).

> This patch, for example, has been submitted multiple times without receiving
> any response, unfortunately.

It can happen, but sending to the right people and possibly resending if
it gets lost is usually sufficient to attract attention. Sending to that
many people make you look like someone feeling so important they need to
shout in a loudspeaker to send orders to everyone. Please refrain from
doing this in the future.

Thanks,
Willy

  reply	other threads:[~2024-12-25 16:00 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  9:42 [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write WangYuli
2024-12-25 13:30 ` Andy Shevchenko
2024-12-25 13:53   ` Kent Overstreet
2024-12-25 16:04     ` Mateusz Guzik
2024-12-25 16:32       ` Kent Overstreet
2024-12-25 17:22         ` Mateusz Guzik
2024-12-25 17:41           ` Kent Overstreet
2024-12-25 15:42   ` WangYuli
2024-12-25 16:00     ` Willy Tarreau [this message]
2024-12-25 16:32       ` WangYuli
2024-12-25 16:56         ` Willy Tarreau
2024-12-26 16:00 ` Oleg Nesterov
2024-12-26 19:02 ` Linus Torvalds
2024-12-26 20:11   ` Oleg Nesterov
2024-12-26 20:29     ` Linus Torvalds
2024-12-26 20:57       ` Oleg Nesterov
2024-12-27 15:54         ` Oleg Nesterov
2024-12-27 16:43           ` Oleg Nesterov
2024-12-27 18:39     ` Manfred Spraul
2024-12-28 14:32       ` Oleg Nesterov
2024-12-28 15:22         ` Oleg Nesterov
2024-12-28 16:32           ` Oleg Nesterov
2024-12-28 18:53             ` Manfred Spraul
2024-12-29 11:54               ` Oleg Nesterov
2024-12-28 16:45           ` Manfred Spraul
2024-12-29 11:57             ` Oleg Nesterov
2024-12-29 12:41               ` Manfred Spraul
2024-12-29 13:05                 ` Oleg Nesterov
2024-12-29 13:13                   ` Oleg Nesterov
2024-12-29 19:54                     ` Manfred Spraul
2024-12-30 15:38                       ` Oleg Nesterov
2024-12-31 11:14                         ` Manfred Spraul
2024-12-31 19:38                           ` Linus Torvalds
2024-12-31 20:24                             ` Oleg Nesterov
2024-12-31 22:31                               ` Linus Torvalds
2025-01-02 13:57                                 ` Oleg Nesterov
2025-01-04 21:15                         ` RFC: Checkpatch: Introduce list of functions that need memory barriers Manfred Spraul

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=20241225160017.GA10283@1wt.eu \
    --to=w@1wt.eu \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangyuli@uniontech.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