From: Jens Axboe <axboe@suse.de>
To: Kedar Sovani <kedars@gmail.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sem2mutex bdev->bd_sem
Date: Thu, 12 Jan 2006 15:36:47 +0100 [thread overview]
Message-ID: <20060112143646.GP3945@suse.de> (raw)
In-Reply-To: <5edf7fc90601120624q46bf0ac6h2b57a09c8ac682ff@mail.gmail.com>
On Thu, Jan 12 2006, Kedar Sovani wrote:
> Strange. It did compile in here w/o a problem.
How could it, when you don't even add bd_mutex to the block_device
structure?
I'd rather just let the patches flow from Ingo's automated setup.
Lessens the chance of problems.
--
Jens Axboe
prev parent reply other threads:[~2006-01-12 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5edf7fc90601120610h70b824ccs9b1ac0fe955dd1b3@mail.gmail.com>
2006-01-12 14:16 ` [PATCH] sem2mutex bdev->bd_sem Jens Axboe
2006-01-12 14:18 ` Arjan van de Ven
2006-01-12 14:19 ` Ingo Molnar
[not found] ` <5edf7fc90601120624q46bf0ac6h2b57a09c8ac682ff@mail.gmail.com>
2006-01-12 14:36 ` 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=20060112143646.GP3945@suse.de \
--to=axboe@suse.de \
--cc=kedars@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).