From: Vinod Koul <vkoul@kernel.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: dmaengine@vger.kernel.org, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
cocci@inria.fr
Subject: Re: [PATCH 0/3] dmaengine: timb_dma: Adjustments for td_alloc_init_desc()
Date: Mon, 22 Jan 2024 17:02:43 +0530 [thread overview]
Message-ID: <Za5SW6xdsOFylD7x@matsya> (raw)
In-Reply-To: <ebd531dd-60e3-4ac3-821e-aa9890960283@web.de>
On 25-12-23, 11:15, Markus Elfring wrote:
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Mon, 25 Dec 2023 11:05:45 +0100
>
> A few update suggestions were taken into account
> from static source code analysis.
was this anaysis done by you or some tool reported this.
Frabkly I dont see much value in these patches, can you fix something
real please
>
> Markus Elfring (3):
> Return directly after a failed kzalloc()
> Improve a size determination
> One function call less after error detection
>
> drivers/dma/timb_dma.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.43.0
--
~Vinod
next prev parent reply other threads:[~2024-01-22 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 10:15 [PATCH 0/3] dmaengine: timb_dma: Adjustments for td_alloc_init_desc() Markus Elfring
2023-12-25 10:18 ` [PATCH 1/3] dmaengine: timb_dma: Return directly after a failed kzalloc() in td_alloc_init_desc() Markus Elfring
2023-12-25 10:20 ` [PATCH 2/3] dmaengine: timb_dma: Improve a size determination " Markus Elfring
2023-12-25 10:22 ` [PATCH 3/3] dmaengine: timb_dma: One function call less in td_alloc_init_desc() after error detection Markus Elfring
2024-01-22 11:32 ` Vinod Koul [this message]
2024-01-22 12:15 ` [0/3] dmaengine: timb_dma: Adjustments for td_alloc_init_desc() Markus Elfring
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=Za5SW6xdsOFylD7x@matsya \
--to=vkoul@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
--cc=dmaengine@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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).