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: Thu, 10 Mar 2016 09:39:03 -0500 [thread overview]
Message-ID: <20160310143903.GF2464@linux.intel.com> (raw)
In-Reply-To: <20160310093750.GA2452@gmail.com>
On Thu, Mar 10, 2016 at 10:37:50AM +0100, Ingo Molnar wrote:
> > > > It seems unfair to ask me to do better than what is there right now.
> > >
> > > It's absolutely fair for maintainers to require the improvement of existing code
> > > you want to modify, especially when you are complicating existing code ...
> >
> > I'm not complicating it. I'm duplicating it.
>
> I don't think your language lawyering is particularly constructive: you are adding
> new functionality to existing x86 code, and as such you need to address review
> feedback from x86 maintainers - even if it involves old code.
Absolutely. But if I've just copied-and-pasted code from elsewhere in
the same file, then I have no obligation to fix style problems. Indeed,
with the variety of styles throughout the kernel, following local style
is clearly the right thing to do for someone who is at best an occasional
contributor to a particular file.
> Anyway, until my concerns are addressed the x86 bits are NAK-ed:
>
> NAKed-by: Ingo Molnar <mingo@kernel.org>
You're adorable. You'd reject this feature over the format of a comment
that you don't like. And you'd rather argue about whether I should fix
the comment than review the patch elsewhere in this thread where I remove
the need for the comment.
It's a good thing Andrea is constructive.
next prev parent reply other threads:[~2016-03-10 14:39 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
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 [this message]
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=20160310143903.GF2464@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.