linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Railton <mark@markrailton.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: boris.ostrovsky@oracle.com, jgross@suse.com,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Drivers: Xen: xlate_mmu.c: Fixed comment layout
Date: Mon, 23 Jul 2018 22:48:04 +0100	[thread overview]
Message-ID: <20180723214804.GA21761@ZeroCool> (raw)
In-Reply-To: <01b221f3-d923-1abb-0168-bfeba80b9a9a@infradead.org>

On Mon, Jul 23, 2018 at 02:44:28PM -0700, Randy Dunlap wrote:
> On 07/23/2018 02:40 PM, Mark Railton wrote:
> > On Mon, Jul 23, 2018 at 02:38:20PM -0700, Randy Dunlap wrote:
> >> On 07/23/2018 02:34 PM, Mark Railton wrote:
> >>> Fixed issue with multi line comment
> >>
> >> Fix [not Fixed]
> >>
> >>>
> >>> Signed-off-by: Mark Railton <mark@markrailton.com>
> >>> ---
> >>>  drivers/xen/xlate_mmu.c | 5 +++--
> >>>  1 file changed, 3 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/xen/xlate_mmu.c b/drivers/xen/xlate_mmu.c
> >>> index 23f1387b3ef7..3b03bc1641ed 100644
> >>> --- a/drivers/xen/xlate_mmu.c
> >>> +++ b/drivers/xen/xlate_mmu.c
> >>> @@ -151,8 +151,9 @@ int xen_xlate_remap_gfn_array(struct vm_area_struct *vma,
> >>>  	struct remap_data data;
> >>>  	unsigned long range = DIV_ROUND_UP(nr, XEN_PFN_PER_PAGE) << PAGE_SHIFT;
> >>>  
> >>> -	/* Kept here for the purpose of making sure code doesn't break
> >>> -	   x86 PVOPS */
> >>> +	/* Kept here for the purpose of making sure code doesn't
> >>> +	 * break x86 PVOPS
> >>> +	 */
> >>
> >> That is still not the preferred kernel multi-line comment style.
> >> Documentation/process/coding-style.rst says:
> >>
> >> 	/*
> >> 	 * This is the preferred style for multi-line
> >> 	 * comments in the Linux kernel source code.
> >> 	 * Please use it consistently.
> >> 	 *
> >> 	 * Description:  A column of asterisks on the left side,
> >> 	 * with beginning and ending almost-blank lines.
> >> 	 */
> >>
> >> although Networking code has a slightly different preferred style (as in
> >> your patch).
> >>
> >>>  	BUG_ON(!((vma->vm_flags & (VM_PFNMAP | VM_IO)) == (VM_PFNMAP | VM_IO)));
> >>>  
> >>>  	data.fgfn = gfn;
> >>>
> >>
> >>
> >> -- 
> >> ~Randy
> > 
> > Thank's for the feedback, I'll get that updated now.
> > 
> > I'm still kinda new to this, I assume I need to send the new patch via
> > git send-email?
> 
> That is one option.  Use whatever works for you.
> 
> There are several email clients that also work well.
> See Documentation/process/email-clients.rst.
> 
> 
> -- 
> ~Randy

From 57c8104d2a30020005be16df2ca69ed66f6c4ae9 Mon Sep 17 00:00:00 2001
From: Mark Railton <mark@markrailton.com>
Date: Mon, 23 Jul 2018 22:28:53 +0100
Subject: [PATCH] Drivers: Xen: xlate_mmu.c: Fixed comment layout

Fixed issue with multi line comment

Signed-off-by: Mark Railton <mark@markrailton.com>
---
 drivers/xen/xlate_mmu.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/xen/xlate_mmu.c b/drivers/xen/xlate_mmu.c
index 23f1387b3ef7..2b77c79f8ce7 100644
--- a/drivers/xen/xlate_mmu.c
+++ b/drivers/xen/xlate_mmu.c
@@ -151,8 +151,10 @@ int xen_xlate_remap_gfn_array(struct vm_area_struct *vma,
 	struct remap_data data;
 	unsigned long range = DIV_ROUND_UP(nr, XEN_PFN_PER_PAGE) << PAGE_SHIFT;

-	/* Kept here for the purpose of making sure code doesn't break
-	   x86 PVOPS */
+	/*
+	 * Kept here for the purpose of making sure code doesn't
+	 * break x86 PVOPS
+	 */
 	BUG_ON(!((vma->vm_flags & (VM_PFNMAP | VM_IO)) == (VM_PFNMAP | VM_IO)));

 	data.fgfn = gfn;
--
2.17.1



  reply	other threads:[~2018-07-23 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 21:34 [PATCH] Drivers: Xen: xlate_mmu.c: Fixed comment layout Mark Railton
2018-07-23 21:38 ` Randy Dunlap
2018-07-23 21:40   ` Mark Railton
2018-07-23 21:44     ` Randy Dunlap
2018-07-23 21:48       ` Mark Railton [this message]
2018-07-23 21:55         ` Randy Dunlap
2018-07-23 21:58           ` Mark Railton

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=20180723214804.GA21761@ZeroCool \
    --to=mark@markrailton.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=xen-devel@lists.xenproject.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).