From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Alexander Beregalov <a.beregalov@gmail.com>,
linux-kernel@vger.kernel.org, gentuu@gmail.com
Subject: Re: [GIT PULL] block updates for 2.6.30-rc1
Date: Tue, 7 Apr 2009 08:38:21 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904070837420.27889@localhost.localdomain> (raw)
In-Reply-To: <20090407114923.GT5178@kernel.dk>
On Tue, 7 Apr 2009, Jens Axboe wrote:
> > I sent you a fix for loop device.
> > http://patchwork.kernel.org/patch/15763/
>
> I missed that the thread had the loop fix as well. I've included it now,
> looks fine to me. Linus, the new diffstat is now:
No, I still see the old diffstat. Did you forget to push out?
Linus
next prev parent reply other threads:[~2009-04-07 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 11:39 [GIT PULL] block updates for 2.6.30-rc1 Jens Axboe
2009-04-07 11:44 ` Alexander Beregalov
2009-04-07 11:49 ` Jens Axboe
2009-04-07 15:38 ` Linus Torvalds [this message]
2009-04-07 17:41 ` Jens Axboe
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=alpine.LFD.2.00.0904070837420.27889@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=a.beregalov@gmail.com \
--cc=gentuu@gmail.com \
--cc=jens.axboe@oracle.com \
--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