From: Arnd Bergmann <arnd@arndb•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Vivek Goyal <vgoyal@redhat•com>, Jens Axboe <axboe@kernel•dk>
Subject: Re: linux-next: manual merge of the bkl-trivial tree with the block tree
Date: Mon, 27 Sep 2010 09:05:02 +0200 [thread overview]
Message-ID: <201009270905.02938.arnd@arndb.de> (raw)
In-Reply-To: <20100927144519.25cd3afa.sfr@canb.auug.org.au>
On Monday 27 September 2010 06:45:19 Stephen Rothwell wrote:
>
> #undef DEBUG
>
> + static DEFINE_MUTEX(ataflop_mutex);
> -static struct request_queue *floppy_queue;
> static struct request *fd_request;
> +static int fdc_queue;
>
> /* Disk types: DD, HD, ED */
> static struct atari_disk_type {
Looks good, thanks!
Vivek, since you are touching that file with other patches, are you interested
in taking the floppy part of my automated block driver BKL removal patch
as well?
I suspect it's possible to come up with a better solution than mine if you
know the code.
Arnd
prev parent reply other threads:[~2010-09-27 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 4:45 linux-next: manual merge of the bkl-trivial tree with the block tree Stephen Rothwell
2010-09-27 7:05 ` Arnd Bergmann [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=201009270905.02938.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vgoyal@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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