public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Kolbjørn Barmen" <linux-m68k@kolla.no>
Cc: Andreas Bombe <aeb@debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amiflop: get rid of sleep_on calls
Date: Sat, 13 Dec 2008 22:30:48 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0812132229560.5728@anakin> (raw)
In-Reply-To: <alpine.LNX.2.00.0812131614360.20992@firda.kolla.no>

On Sat, 13 Dec 2008, Kolbjørn Barmen wrote:
> On Tue, 9 Dec 2008, Geert Uytterhoeven wrote:
> > > The complete_all() with INIT_COMPLETION() was because I'm not sure about
> > > whether fd_motor_on() might run concurrently.  Better safe than sorry.
> > 
> > I'm afraid my Amiga floppy drive doesn't work anymore...
> > Any other testers available?
> 
> I have some, even enough external ones to chain up to the max of 4
> floppy drives (floppy raid anyone? :)). What needs to be tested?

That the floppy drive still works(tm)? ;-)

> I havent updated kernel for quite some time (still running 2.6.22),
> should I now pull sources from git or what?

I haven't applied Andreas' patch yet, so you should pull the sources from git
and apply his patch.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-12-13 21:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 16:59 [PATCH] amiflop: get rid of sleep_on calls Andreas Bombe
2008-12-09  8:26 ` Joerg Dorchain
2008-12-10  0:48   ` Andreas Bombe
2008-12-10  8:16     ` Joerg Dorchain
2008-12-16 20:23   ` Geert Uytterhoeven
2008-12-17  8:00     ` Joerg Dorchain
2008-12-09  8:31 ` Geert Uytterhoeven
2008-12-09 18:34   ` Andreas Bombe
2008-12-10  1:02   ` [PATCH v2] " Andreas Bombe
2008-12-14 16:21     ` Geert Uytterhoeven
2008-12-23 14:22       ` Andreas Bombe
2008-12-31 16:30         ` Geert Uytterhoeven
2008-12-13 15:20   ` [PATCH] " Kolbjørn Barmen
2008-12-13 21:30     ` Geert Uytterhoeven [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=Pine.LNX.4.64.0812132229560.5728@anakin \
    --to=geert@linux-m68k.org \
    --cc=aeb@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@kolla.no \
    --cc=linux-m68k@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