From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Trent Waddington <trent.waddington@gmail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: [PATCH][0/5] floppy.c: first round of cleanup patches - the simple stuff
Date: Tue, 6 Feb 2007 11:41:52 +0000 [thread overview]
Message-ID: <20070206114152.4b622e40@localhost.localdomain> (raw)
In-Reply-To: <200702060028.31691.jesper.juhl@gmail.com>
On Tue, 6 Feb 2007 00:28:31 +0100
Jesper Juhl <jesper.juhl@gmail.com> wrote:
> Greetings people,
>
> Here is, as promised, the first round of cleanup patches for floppy.c
> (more will follow later).
>
> I opted to start with the simple stuff first, both to get it out of the way
> and also to get something done resonably fast, so don't expect anything
> earth shattering in this first series.
>
> There are 5 patches in this series. They are based on 2.6.20 and are
> incremental.
>
> These are the patches (they'll be posted to the same recipients as this initial mail) :
>
> [PATCH][1/5] floppy.c: Initial (partial) CodingStyle cleanup
> [PATCH][2/5] floppy.c: Remove pointless register keywords
> [PATCH][3/5] floppy.c: Remove dead/commented out code
> [PATCH][4/5] floppy.c: Add explicit/better printk() levels
> [PATCH][5/5] floppy.c: Fix device_create_file() warning
Acked-by: Alan Cox <alan@redhat.com>
for the set of 5 patches. Its a beginning and removing the dead wood so
you can see what is actually there is a good a beginning as any other.
next prev parent reply other threads:[~2007-02-06 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 23:28 [PATCH][0/5] floppy.c: first round of cleanup patches - the simple stuff Jesper Juhl
2007-02-06 8:06 ` Andi Kleen
2007-02-06 9:15 ` Jesper Juhl
2007-02-06 11:41 ` Alan [this message]
[not found] ` <58cb370e0702061458u41f0a108n1eeae03770433bbf@mail.gmail.com>
2007-02-06 23:15 ` Bartlomiej Zolnierkiewicz
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=20070206114152.4b622e40@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ak@suse.de \
--cc=bzolnier@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trent.waddington@gmail.com \
/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