From: Ralf Baechle <ralf@linux-mips.org>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 42/66] arch/mips/lib/libgcc.h: Checkpatch cleanup
Date: Wed, 17 Mar 2010 15:51:28 +0000 [thread overview]
Message-ID: <20100317155126.GE4554@linux-mips.org> (raw)
In-Reply-To: <9cdbb57f1003020713x4e897af9ka87e348bf782f380@mail.gmail.com>
On Tue, Mar 02, 2010 at 04:13:11PM +0100, Andrea Gelmini wrote:
> 2010/3/1 Paul Mundt <lethal@linux-sh.org>:
> Hi Paul,
> thanks for your reply.
>
> > I'll apply the sh part by itself, and I suppose Ralf will do the same for
> > MIPS. I'm a bit confused as to why these were lumped together when 65 out
> > of 66 oneliner patches made no use of ad-hoc grouping.
>
> After the experience with GregKH, I was looking for others maintainer
> interested in code cleanup. So I sent some patches over random files.
> If you care, I can checkpatch.pl all mips subtree and send you patches (if any).
Feel free to - but remember that the coding style document is a guideline
not something to be followed unconditionally.
Ralf
next prev parent reply other threads:[~2010-03-17 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1267289508-31031-1-git-send-email-andrea.gelmini@gelma.net>
2010-02-27 16:51 ` [PATCH 42/66] arch/mips/lib/libgcc.h: Checkpatch cleanup Andrea Gelmini
2010-03-01 2:33 ` Paul Mundt
2010-03-02 15:13 ` Andrea Gelmini
2010-03-17 15:51 ` Ralf Baechle [this message]
2010-03-17 15:39 ` Ralf Baechle
2010-02-27 16:51 ` [PATCH 55/66] arch/sh/boot/compressed/cache.c: " Andrea Gelmini
2010-03-02 3:13 ` Paul Mundt
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=20100317155126.GE4554@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=andrea.gelmini@gelma.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@vger.kernel.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).