mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Haoxiang Li <make24@iscas.ac.cn>,
	megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
	kernel-janitors@vger.kernel.org,
	Chandrakanth patil <chandrakanth.patil@broadcom.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Kashyap Desai <kashyap.desai@broadcom.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Shivasharan Srikanteshwara
	<shivasharan.srikanteshwara@broadcom.com>,
	Sumit Saxena <sumit.saxena@broadcom.com>,
	Suraj Upadhyay <usuraj35@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: scsi: megaraid: Add missing check for dma_set_mask
Date: Mon, 1 Jul 2024 14:12:33 +0200	[thread overview]
Message-ID: <e751f992-0510-478e-a714-6299e8650333@web.de> (raw)
In-Reply-To: <20240701034102.84207-1-make24@iscas.ac.cn>

> pdev->dev cannot perform DMA properly if dma_set_mask() returns non-zero.

Can a wording approach (like the following) become a part of a better change description?

  Direct memory access can not be properly performed any more
  after a dma_set_mask() call failed.


> Add check for dma_set_mask()

How do you think about to avoid a repeated reference to a function name?


>                                  return the error if it fails.

How can this happen after you did not store the return value (in the local variable “error”)
for further usage (according to your proposed source code adjustment)?


…
> Signed-off-by: Haoxiang Li <make24@iscas.ac.cn>

I find it interesting that another personal name is presented here.
I noticed that some patches were published with the name “Ma Ke” previously.
How will requirements be resolved for the Developer's Certificate of Origin?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc6#n398


How do you think about to use a summary phrase like “Complete error handling
in megaraid_probe_one()”?

Regards,
Markus

      reply	other threads:[~2024-07-01 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  3:41 Haoxiang Li
2024-07-01 12:12 ` Markus Elfring [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=e751f992-0510-478e-a714-6299e8650333@web.de \
    --to=markus.elfring@web.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=chandrakanth.patil@broadcom.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=make24@iscas.ac.cn \
    --cc=martin.petersen@oracle.com \
    --cc=megaraidlinux.pdl@broadcom.com \
    --cc=shivasharan.srikanteshwara@broadcom.com \
    --cc=sumit.saxena@broadcom.com \
    --cc=usuraj35@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

all inboxes | Powered by JetHome®