From: Markus Elfring <Markus.Elfring@web.de>
To: Vasiliy Kovalev <kovalev@altlinux.org>, linux-fsdevel@vger.kernel.org
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
lvc-patches@linuxtesting.org,
"Tigran A. Aivazian" <aivazian.tigran@gmail.com>,
dutyrok@altlinux.org
Subject: Re: [PATCH v2 fs/bfs 0/2] bfs: fix null-ptr-deref and possible warning in bfs_move_block() func
Date: Thu, 11 Jul 2024 09:47:01 +0200 [thread overview]
Message-ID: <5c191e5d-b64c-4e3c-9f70-9cd3371a3142@web.de> (raw)
In-Reply-To: <20240711073238.44399-1-kovalev@altlinux.org>
…
> [PATCHv2 fs/bfs 1/2] bfs: prevent null pointer dereference in bfs_move_block()
…
I find it usually helpful to separate the version identifier from the previous key word.
How do you think about to improve the outline another bit (also for the cover letter)?
Regards,
Markus
next prev parent reply other threads:[~2024-07-11 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 7:32 [PATCHv2 fs/bfs 0/2] bfs: fix null-ptr-deref and possible warning in bfs_move_block() func kovalev
2024-07-11 7:32 ` [PATCHv2 fs/bfs 1/2] bfs: prevent null pointer dereference in bfs_move_block() kovalev
2024-07-11 7:32 ` [PATCHv2 fs/bfs 2/2] bfs: add buffer_uptodate check before mark_buffer_dirty call kovalev
2024-07-11 7:47 ` Markus Elfring [this message]
2024-07-11 8:13 ` [PATCH v2 fs/bfs 0/2] bfs: fix null-ptr-deref and possible warning in bfs_move_block() func kovalev
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=5c191e5d-b64c-4e3c-9f70-9cd3371a3142@web.de \
--to=markus.elfring@web.de \
--cc=aivazian.tigran@gmail.com \
--cc=dutyrok@altlinux.org \
--cc=kovalev@altlinux.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-patches@linuxtesting.org \
--cc=stable@vger.kernel.org \
/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).