All of
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <>
To: Randy Dunlap <>
	James Smart <>,
	Ram Vegesna <>,,
	"James E.J. Bottomley" <>,
	"Martin K. Petersen" <>
Subject: Re: [PATCH] scsi: elx: libefc_sli: use "/*" for non-kernel-doc comment
Date: Mon, 23 Jan 2023 20:54:10 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Randy Dunlap's message of "Mon, 16 Jan 2023 23:01:51 -0800")


> Don't use "/**" to begin non-kernel-doc comments.
> Prevent a kernel-doc warning:
> drivers/scsi/elx/libefc_sli/sli4.c:13: warning: cannot understand function prototype: 'struct sli4_asic_entry_t sli4_asic_table[] = '

Applied to 6.3/scsi-staging, thanks!

Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2023-01-24  1:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  7:01 [PATCH] scsi: elx: libefc_sli: use "/*" for non-kernel-doc comment Randy Dunlap
2023-01-24  1:54 ` Martin K. Petersen [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.