From: kovalev@altlinux.org
To: Markus Elfring <Markus.Elfring@web.de>
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, linux-fsdevel@vger.kernel.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 11:13:57 +0300 [thread overview]
Message-ID: <4bf1acdd-9ab3-2e83-d491-79039c6d0e92@basealt.ru> (raw)
In-Reply-To: <5c191e5d-b64c-4e3c-9f70-9cd3371a3142@web.de>
11.07.2024 10:47, Markus Elfring wrote:
> …
>> [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)?
I will take your recommendation into account when submitting the next
versions, if there are any comments on the patches themselves.
> Regards,
> Markus
--
Thanks,
Vasiliy Kovalev
prev parent reply other threads:[~2024-07-11 8:14 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 ` [PATCH v2 fs/bfs 0/2] bfs: fix null-ptr-deref and possible warning in bfs_move_block() func Markus Elfring
2024-07-11 8:13 ` kovalev [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=4bf1acdd-9ab3-2e83-d491-79039c6d0e92@basealt.ru \
--to=kovalev@altlinux.org \
--cc=Markus.Elfring@web.de \
--cc=aivazian.tigran@gmail.com \
--cc=dutyrok@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).