From: Jens Axboe <axboe@suse.de>
To: mikem <mikem@beardog.cca.cpqcorp.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: cciss update [1/8] ioctl32 fix
Date: Tue, 10 Aug 2004 18:25:11 +0200 [thread overview]
Message-ID: <20040810162510.GB15091@suse.de> (raw)
In-Reply-To: <20040810160140.GA19909@beardog.cca.cpqcorp.net>
On Tue, Aug 10 2004, mikem wrote:
> My latest updates are not in 2.6.8-rc4. So I am resubmitting them.
They are in -mm, it's customary for patches for misc drivers to go
through there and be fed to Linus by Andrew after a little while. So if
they are in -mm, you can consider them safely on their way to Linus.
I've never seen Andrew drop patches from -mm without first asking.
--
Jens Axboe
prev parent reply other threads:[~2004-08-10 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 16:01 cciss update [1/8] ioctl32 fix mikem
2004-08-10 16:25 ` Jens Axboe [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=20040810162510.GB15091@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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