linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Mezgani Ali <ali.mezgani@gmail.com>
Cc: Ameer Hamza <ahamza@ixsystems.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Jeff Layton <jlayton@kernel.org>,
	chuck.lever@oracle.com, arnd@arndb.de, guoren@kernel.org,
	palmer@rivosinc.com, f.fainelli@gmail.com, slark_xiao@163.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, awalker@ixsystems.com,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Add new open(2) flag - O_EMPTY_PATH
Date: Wed, 19 Apr 2023 11:18:28 +0200	[thread overview]
Message-ID: <20230419-dachorganisation-infozentrum-40a4234d6a4c@brauner> (raw)
In-Reply-To: <7454A798-1277-411A-853C-635B33439029@gmail.com>

On Wed, Apr 19, 2023 at 01:46:16AM +0000, Mezgani Ali wrote:
> Look Hamza,
> 
> The style you’re writing with project a reader of drafts and IETF documents.
> Interesting what you are doing here in Kernel files.
> 
> But let me tell you I suspect you are a hyper virtualized Moroccan ( Hypocrite ).
> 
> One solution you have HR and leave.

Nonsensical off-topic mails like this with thinly veiled personal
attacks are not acceptable. So stop it.

  parent reply	other threads:[~2023-04-19  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 16:02 [PATCH] Add new open(2) flag - O_EMPTY_PATH Ameer Hamza
2022-12-31  0:15 ` kernel test robot
2022-12-31 23:56   ` [PATCH v2] " Ameer Hamza
2023-01-01 11:16     ` kernel test robot
2023-01-01 15:37       ` [PATCH v3] " Ameer Hamza
2023-01-02 14:01     ` [PATCH v2] " David Laight
2023-01-02 14:35       ` Ameer Hamza
2023-01-06  9:21         ` David Laight
2023-01-06 13:06 ` [PATCH] " Christian Brauner
2023-04-19  1:15   ` Ameer Hamza
     [not found]     ` <7454A798-1277-411A-853C-635B33439029@gmail.com>
2023-04-19  9:18       ` Christian Brauner [this message]
2023-04-19 21:29     ` David Laight
2023-04-26 13:10       ` Andrew Walker

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=20230419-dachorganisation-infozentrum-40a4234d6a4c@brauner \
    --to=brauner@kernel.org \
    --cc=ahamza@ixsystems.com \
    --cc=ali.mezgani@gmail.com \
    --cc=arnd@arndb.de \
    --cc=awalker@ixsystems.com \
    --cc=chuck.lever@oracle.com \
    --cc=f.fainelli@gmail.com \
    --cc=guoren@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palmer@rivosinc.com \
    --cc=slark_xiao@163.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).