From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Chunyan Zhang <chunyan.zhang@unisoc.com>,
linux-serial@vger.kernel.org, kernel-janitors@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Jiri Slaby <jirislaby@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Chunyan Zhang <zhang.lyra@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>
Subject: Re: [PATCH 2/2] serial: sprd: Fix DMA buffer leak issue
Date: Mon, 10 Jul 2023 15:30:13 +0200 [thread overview]
Message-ID: <2023071047-dragster-shortly-981a@gregkh> (raw)
In-Reply-To: <69d56da8-9530-e729-d527-89879d2bab06@web.de>
On Mon, Jul 10, 2023 at 01:36:07PM +0200, Markus Elfring wrote:
> > Release DMA buffer when _probe() returns fail to avoid memory leak.
>
> I would appreciate if this change description can be improved another bit.
Again, I would appreciate it if you do not provide reviews for any
kernel subsystems in which I am a maintainer of.
Please stop, it is not helpful at all.
greg k-h
next prev parent reply other threads:[~2023-07-10 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 8:03 [PATCH 1/2] serial: sprd: Assign sprd_port after initialized to avoid wrong access Chunyan Zhang
2023-07-10 8:03 ` [PATCH 2/2] serial: sprd: Fix DMA buffer leak issue Chunyan Zhang
2023-07-10 10:03 ` Baolin Wang
[not found] ` <69d56da8-9530-e729-d527-89879d2bab06@web.de>
2023-07-10 13:30 ` Greg Kroah-Hartman [this message]
2023-07-11 2:58 ` Chunyan Zhang
2023-07-10 9:57 ` [PATCH 1/2] serial: sprd: Assign sprd_port after initialized to avoid wrong access Baolin Wang
2023-07-11 2:57 ` Chunyan Zhang
2023-07-12 1:39 ` Baolin Wang
2023-07-12 3:11 ` Chunyan Zhang
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=2023071047-dragster-shortly-981a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Markus.Elfring@web.de \
--cc=baolin.wang@linux.alibaba.com \
--cc=chunyan.zhang@unisoc.com \
--cc=jirislaby@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox