From: Matthew Wilcox <willy@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: akpm@linux-foundation.org, hpa@zytor.com, mingo@elte.hu,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: + x86-add-support-for-pud-sized-transparent-hugepages-checkpatch-fixes.patch added to -mm tree
Date: Fri, 4 Mar 2016 15:30:18 -0500 [thread overview]
Message-ID: <20160304203018.GC5530@linux.intel.com> (raw)
In-Reply-To: <20160203074835.GB32652@gmail.com>
On Wed, Feb 03, 2016 at 08:48:35AM +0100, Ingo Molnar wrote:
> > @@ -111,8 +111,10 @@ static inline pud_t native_pudp_get_and_
> > #ifdef CONFIG_SMP
> > return native_make_pud(xchg(&pudp->pud, 0));
> > #else
> > - /* native_local_pudp_get_and_clear,
> > - but duplicated because of cyclic dependency */
> > + /*
> > + * native_local_pudp_get_and_clear, but duplicated because of cyclic
> > + * dependency
> > + */
> > pud_t ret = *pudp;
> > native_pud_clear(pudp);
> > return ret;
>
> When referring to functions in comments (or changelogs) please use () to make it
> clear on sight what is being referred to.
>
> Also, please try to construct proper English sentences with verbs and such!
>
> I.e. something like this would work for me:
>
> > + /*
> > + * This is a duplicate of native_local_pudp_get_and_clear(),
> > + * because we cannot use the original due to a cyclic header
> > + * file dependency:
> > + */
>
> (Assuming I managed to decode the shorthand form properly.)
I have no idea what it means. This is copy-and-change of the pmd version,
which was originally commit db3eb96f4e6281b84dd33c8980dacc27f2efe177 by
Andrea.
It seems unfair to ask me to do better than what is there right now.
next prev parent reply other threads:[~2016-03-04 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 22:53 + x86-add-support-for-pud-sized-transparent-hugepages-checkpatch-fixes.patch added to -mm tree akpm
2016-02-03 7:48 ` Ingo Molnar
2016-03-04 20:30 ` Matthew Wilcox [this message]
2016-03-09 12:08 ` Ingo Molnar
2016-03-09 16:55 ` Matthew Wilcox
2016-03-10 9:37 ` Ingo Molnar
2016-03-10 14:39 ` Matthew Wilcox
2016-03-09 17:40 ` Andrea Arcangeli
2016-03-09 18:45 ` Matthew Wilcox
2016-03-09 20:03 ` Matthew Wilcox
2016-03-09 23:08 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2016-01-27 20:30 akpm
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=20160304203018.GC5530@linux.intel.com \
--to=willy@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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.