mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sudhip Nashi <sudhip@nashi.us>
To: axboe@kernel.dk
Cc: Arnd Bergmann <arnd@arndb.de>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	Petr Mladek <pmladek@suse.com>, Sudhip Nashi <sudhip@nashi.us>,
	Adam Williamson <awilliam@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] gdrom: Block comments use a trailing */ on a separate line
Date: Fri, 19 Jun 2020 16:18:21 -0500	[thread overview]
Message-ID: <20200619211819.50910-1-sudhip@nashi.us> (raw)

Fix code style to conform with linux coding standards

Signed-off-by: Sudhip Nashi <sudhip@nashi.us>
---
 drivers/cdrom/gdrom.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/cdrom/gdrom.c b/drivers/cdrom/gdrom.c
index 09b0cd292720..9707f04b54a3 100644
--- a/drivers/cdrom/gdrom.c
+++ b/drivers/cdrom/gdrom.c
@@ -692,13 +692,15 @@ static int gdrom_init_dma_mode(void)
 	__raw_writeb(0xEF, GDROM_STATUSCOMMAND_REG);
 	if (!gdrom_wait_busy_sleeps())
 		return -EBUSY;
-	/* Memory protection setting for GDROM DMA
+       /*
+	* Memory protection setting for GDROM DMA
 	* Bits 31 - 16 security: 0x8843
 	* Bits 15 and 7 reserved (0)
 	* Bits 14 - 8 start of transfer range in 1 MB blocks OR'ed with 0x80
 	* Bits 6 - 0 end of transfer range in 1 MB blocks OR'ed with 0x80
 	* (0x40 | 0x80) = start range at 0x0C000000
-	* (0x7F | 0x80) = end range at 0x0FFFFFFF */
+	* (0x7F | 0x80) = end range at 0x0FFFFFFF
+	*/
 	__raw_writel(0x8843407F, GDROM_DMA_ACCESS_CTRL_REG);
 	__raw_writel(9, GDROM_DMA_WAIT_REG); /* DMA word setting */
 	return 0;
-- 
2.27.0


             reply	other threads:[~2020-06-19 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 21:18 Sudhip Nashi [this message]
2020-06-19 21:25 ` Jens Axboe

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=20200619211819.50910-1-sudhip@nashi.us \
    --to=sudhip@nashi.us \
    --cc=arnd@arndb.de \
    --cc=awilliam@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=wangkefeng.wang@huawei.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®