kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: linux-block@vger.kernel.org, kernel-janitors@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Chun-Yi Lee <joeyli.kernel@gmail.com>,
	"David S . Miller" <davem@davemloft.net>,
	Jens Axboe <axboe@kernel.dk>, Justin Sanders <justin@coraid.com>,
	Kirill Korotaev <dev@openvz.org>,
	Nicolai Stange <nstange@suse.com>,
	Pavel Emelianov <xemul@openvz.org>
Subject: Re: [PATCH v2] aoe: fix the potential use-after-free problem in more places
Date: Wed, 15 May 2024 13:09:32 +0800	[thread overview]
Message-ID: <20240515050932.GG4433@linux-l9pv.suse> (raw)
In-Reply-To: <e8331545-d261-44af-b500-93b90d77d8b7@web.de>

Hi Markus,

On Tue, May 14, 2024 at 05:34:57PM +0200, Markus Elfring wrote:
> I suggest to reconsider the version identification in this patch subject
> once more.
> 
> 
> …
> > This patch makes the above functions do …
> 
> Do you stumble still on wording challenges for improved change descriptions
> in your patches?
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.9#n94
> 
> …
> > ---
> >
> > v2:
> > - Improve patch description
> 
> V3:
> ???
> 
> V4:
> ???
> 
> Would you like to include issue reporters in message recipient lists?
> 
> Regards,
> Markus

I will wait more suggestion for code side and send new version.

Thanks a lot!
Joey Lee 

      reply	other threads:[~2024-05-15  5:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240514151854.13066-1-jlee@suse.com>
2024-05-14 15:34 ` [PATCH v2] aoe: fix the potential use-after-free problem in more places Markus Elfring
2024-05-15  5:09   ` joeyli [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=20240515050932.GG4433@linux-l9pv.suse \
    --to=jlee@suse.com \
    --cc=Markus.Elfring@web.de \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=dev@openvz.org \
    --cc=joeyli.kernel@gmail.com \
    --cc=justin@coraid.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nstange@suse.com \
    --cc=xemul@openvz.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).