From: Jeff Garzik <jeff@garzik.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: unsik Kim <donari75@gmail.com>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 3/3] mg_disk: use defines from <linux/ata.h>
Date: Sun, 26 Apr 2009 00:05:08 -0400 [thread overview]
Message-ID: <49F3DD74.9030609@garzik.org> (raw)
In-Reply-To: <200904251510.03924.bzolnier@gmail.com>
Bartlomiej Zolnierkiewicz wrote:
> While at it:
> - remove MG_REG_HEAD_MUST_BE_ON define
> - remove MG_REG_CTRL_INTR_ENABLE define
> - remove MG_REG_HEAD_LBA_MODE define
> - remove unused defines
>
> Cc: unsik Kim <donari75@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> ---
> drivers/block/mg_disk.c | 143 ++++++++++++++----------------------------------
> 1 file changed, 43 insertions(+), 100 deletions(-)
ACK
parent reply other threads:[~2009-04-26 4:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200904251510.03924.bzolnier@gmail.com>]
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=49F3DD74.9030609@garzik.org \
--to=jeff@garzik.org \
--cc=bzolnier@gmail.com \
--cc=donari75@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).