From: Richard Weinberger <richard.weinberger@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
mm-commits@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: mmotm 2014-10-29-14-19 uploaded
Date: Thu, 30 Oct 2014 10:02:15 +0100 [thread overview]
Message-ID: <CAFLxGvwGRz8Z2=eD53VjVgUf5zdM3KCyLcUZN1g_Po2D2xQ4DA@mail.gmail.com> (raw)
In-Reply-To: <1414619976.2542.1.camel@perches.com>
On Wed, Oct 29, 2014 at 10:59 PM, Joe Perches <joe@perches.com> wrote:
> On Wed, 2014-10-29 at 22:37 +0100, Thomas Gleixner wrote:
>> On Wed, 29 Oct 2014, akpm@linux-foundation.org wrote:
>> > This mmotm tree contains the following patches against 3.18-rc2:
>> > (patches marked "*" will be included in linux-next)
>> >
>> > * kernel-posix-timersc-code-clean-up.patch
>>
>> Can you please drop this pointless churn? We really can replace all
>> that stuff with a shell script and let it run over the tree every now
>> and then.
>
> Should any automated code reformatting really be done
> by an unsupervised or unreviewed shell script?
As many users of "checkpatch.pl -f" behave anyway like
unsupervised/unreviewed shell scripts
it would not matter. ;-)
--
Thanks,
//richard
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-10-30 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 21:20 akpm
2014-10-29 21:37 ` Thomas Gleixner
2014-10-29 21:59 ` Joe Perches
2014-10-30 9:02 ` Richard Weinberger [this message]
2014-10-30 8:47 ` [PATCH] mm-cma-make-kmemleak-ignore-cma-regions-fix Michal Hocko
2014-10-30 8:56 ` Michal Hocko
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='CAFLxGvwGRz8Z2=eD53VjVgUf5zdM3KCyLcUZN1g_Po2D2xQ4DA@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox