public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: Tejun Heo <tj@kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [bisected] 2.6.39 breaks floppy
Date: Wed, 25 May 2011 21:37:34 +0200	[thread overview]
Message-ID: <4DDD5A7E.4030903@fusionio.com> (raw)
In-Reply-To: <201105252116.37839.linux@rainbow-software.org>

On 2011-05-25 21:16, Ondrej Zary wrote:
> Hello,
> floppy stopped working in 2.6.39 (confirmed on two machines). 2.6.38 worked 
> fine. 
> /dev/fd0 is created but does not work (mdir says: "No such device or address", 
> mount says "/dev/fd0 is not a valid block device"). dmesg shows no errors:
> 
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> 
> Bisected it to 9fd097b14918875bd6f125ed699d7bbbba5893ee
> (block: unexport DISK_EVENT_MEDIA_CHANGE for legacy/fringe drivers)
> 
> Adding the removed line back to floppy.c fixes the problem.

Tejun?

-- 
Jens Axboe


  reply	other threads:[~2011-05-25 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 19:16 [bisected] 2.6.39 breaks floppy Ondrej Zary
2011-05-25 19:37 ` Jens Axboe [this message]
2011-05-25 20:54   ` 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=4DDD5A7E.4030903@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=tj@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