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:40:11 +0100 [thread overview]
Message-ID: <20180723214011.GA21167@ZeroCool> (raw)
In-Reply-To: <e0b30ab8-d418-cbe0-d03c-a0aee1d48367@infradead.org>
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?
Thanks,
Mark
next prev parent reply other threads:[~2018-07-23 21:40 UTC|newest]
Thread overview: 14+ 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:38 ` Randy Dunlap
2018-07-23 21:40 ` Mark Railton
2018-07-23 21:40 ` Mark Railton [this message]
2018-07-23 21:44 ` Randy Dunlap
2018-07-23 21:44 ` Randy Dunlap
2018-07-23 21:48 ` Mark Railton
2018-07-23 21:48 ` Mark Railton
2018-07-23 21:55 ` Randy Dunlap
2018-07-23 21:55 ` Randy Dunlap
2018-07-23 21:58 ` Mark Railton
2018-07-23 21:58 ` Mark Railton
-- strict thread matches above, loose matches on Subject: below --
2018-07-23 21:34 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=20180723214011.GA21167@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 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.