From: Tejun Heo <tj@home-tj.org>
To: Tejun Heo <tj@home-tj.org>
Cc: bzolnier@gmail.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.11-rc2] ide: driver updates (phase 2)
Date: Sat, 05 Feb 2005 18:53:10 +0900 [thread overview]
Message-ID: <42049786.2060505@home-tj.org> (raw)
In-Reply-To: <20050205021502.GA17767@htj.dyndns.org>
Oops, I accidentally put ", ," in the To: line of all the mails which
contain patches, and they don't show up on the lkml. I'll post the
patches again.
Bartlomiej, if you got the first set of patches, please ignore them.
The contents are identical, so if you've already reviewed them, you
don't have to verify the new set. I'm really sorry. As I've been
making quite a few mistakes during mailing patches manually, I've
written a script to do it, but I still manage to make mistakes. :-(
--
tejun
next prev parent reply other threads:[~2005-02-05 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 2:15 [PATCH 2.6.11-rc2] ide: driver updates (phase 2) Tejun Heo
2005-02-05 9:53 ` Tejun Heo [this message]
2005-02-05 10:14 ` Tejun Heo
[not found] ` <20050205021555.F3D161326FA@htj.dyndns.org>
2005-02-06 13:20 ` [PATCH 2.6.11-rc2 01/09] ide: kill unused pkt_task_t Bartlomiej Zolnierkiewicz
[not found] ` <20050205021556.8FC05132701@htj.dyndns.org>
2005-02-06 18:34 ` [PATCH 2.6.11-rc2 04/09] ide: convert REQ_DRIVE_TASK to REQ_DRIVE_TASKFILE Bartlomiej Zolnierkiewicz
2005-02-07 5:13 ` Tejun Heo
[not found] ` <20050205021556.CFCE41326F9@htj.dyndns.org>
2005-02-06 18:38 ` [PATCH 2.6.11-rc2 05/09] ide: map ide_task_ioctl() to ide_taskfile_ioctl() Bartlomiej Zolnierkiewicz
2005-02-07 5:04 ` Tejun Heo
[not found] ` <20050205021557.6A692132705@htj.dyndns.org>
2005-02-06 18:46 ` [PATCH 2.6.11-rc2 08/09] ide: map ide_cmd_ioctl() " Bartlomiej Zolnierkiewicz
2005-02-07 5:02 ` Tejun Heo
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=42049786.2060505@home-tj.org \
--to=tj@home-tj.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).