From: "Dan Williams" <dan.j.williams@gmail.com>
To: "Neil Brown" <neilb@suse.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: raid5: coding style cleanup / refactor
Date: Fri, 15 Jun 2007 16:55:05 -0700 [thread overview]
Message-ID: <e9c3a7c20706151655j6cdc5307qe544b8a3a2f156a4@mail.gmail.com> (raw)
In-Reply-To: <18035.5414.680663.405523@notabene.brown>
On 6/15/07, Neil Brown <neilb@suse.de> wrote:
> Good idea... Am I asking too much to have separate things in separate
> patches? It makes review easier.
>
...yeah I got a little bit carried away after the refactoring. I will
spin the refactoring out into a separate patch and handle the coding
style violations as you suggested.
> NeilBrown
Thanks,
Dan
prev parent reply other threads:[~2007-06-15 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 17:41 raid5: coding style cleanup / refactor Dan Williams
2007-06-12 21:25 ` Andrew Morton
2007-06-12 21:32 ` Williams, Dan J
2007-06-12 22:09 ` Dan Williams
2007-06-13 18:53 ` Dan Williams
2007-06-14 21:08 ` Bill Davidsen
2007-06-15 2:39 ` Dan Williams
2007-06-15 22:39 ` Neil Brown
2007-06-15 23:55 ` Dan Williams [this message]
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=e9c3a7c20706151655j6cdc5307qe544b8a3a2f156a4@mail.gmail.com \
--to=dan.j.williams@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.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;
as well as URLs for NNTP newsgroup(s).