From: Al Viro <viro@zeniv.linux.org.uk>
To: Mattia Massarenti <mattiamassarenti.mm@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] add documentation for function parameter
Date: Wed, 3 Sep 2025 06:41:36 +0100 [thread overview]
Message-ID: <20250903054136.GJ39973@ZenIV> (raw)
In-Reply-To: <CAEMaYNJP_QWV9NkD9stdODfGgvZQX_yUBzqZQ5cr5-u_g9Tg2g@mail.gmail.com>
On Sun, Aug 31, 2025 at 06:59:47PM +0200, Mattia Massarenti wrote:
> Please, ignore this patch, I did a mistake including in the commit also my
> log file. Should I send a new email with the correct patch?
What you probably should do is
* check if (and how many times) had such a patch been posted
* check if one of the earlier patches got applied, and when had that
happened. Check linux-next...
prev parent reply other threads:[~2025-09-03 5:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-31 16:53 [PATCH] add documentation for function parameter Mattia Massarenti
[not found] ` <CAEMaYNJP_QWV9NkD9stdODfGgvZQX_yUBzqZQ5cr5-u_g9Tg2g@mail.gmail.com>
2025-09-03 5:41 ` Al Viro [this message]
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=20250903054136.GJ39973@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattiamassarenti.mm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.