From: Alessio Faina <alessio.faina@canonical.com>
To: David Howells <dhowells@redhat.com>
Cc: kernel-esm-reviews@groups.canonical.com,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [SRU][B][PATCH 1/1] afs: Fix lock recursion
Date: Tue, 21 Oct 2025 12:05:33 +0200 [thread overview]
Message-ID: <aPda7Q5EvcabyS8c@cicciput> (raw)
In-Reply-To: <1475047.1761040626@warthog.procyon.org.uk>
On Tue, Oct 21, 2025 at 10:57:06AM +0100, David Howells wrote:
> Alessio Faina <alessio.faina@canonical.com> wrote:
>
> > To: kernel-esm-reviews@groups.canonical.com
>
> Did you mean to cc everyone on this?
>
> David
>
No I forgot --no-cc --no-bcc while running git send-mail, I'm really
sorry for the spam.
- Alessio
prev parent reply other threads:[~2025-10-21 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251020081733.18036-1-alessio.faina@canonical.com>
2025-10-20 8:17 ` [SRU][B][PATCH 1/1] afs: Fix lock recursion Alessio Faina
2025-10-21 9:57 ` David Howells
2025-10-21 10:05 ` Alessio Faina [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=aPda7Q5EvcabyS8c@cicciput \
--to=alessio.faina@canonical.com \
--cc=dhowells@redhat.com \
--cc=kernel-esm-reviews@groups.canonical.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=marc.dionne@auristor.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;
as well as URLs for NNTP newsgroup(s).