The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Stephen Hemminger <shemminger@vyatta.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	Pekka Enberg <penberg@kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>, Tejun Heo <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] block driver updates for 2.6.38
Date: Fri, 14 Jan 2011 07:55:25 -0800 (PST)	[thread overview]
Message-ID: <940009.55868.qm@web113320.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20110113224228.3f7ae374@s6510>

----- Original Message ----

> From: Stephen Hemminger <shemminger@vyatta.com>
> To: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Jens Axboe <jaxboe@fusionio.com>; Pekka Enberg <penberg@kernel.org>; 
>Marcelo Tosatti <mtosatti@redhat.com>; Tejun Heo <tj@kernel.org>; 
>"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
> Sent: Fri, January 14, 2011 7:42:28 AM
> Subject: Re: [GIT PULL] block driver updates for 2.6.38
> 
> On Thu, 13 Jan 2011 17:03:21 -0800
> Linus Torvalds <torvalds@linux-foundation.org>  wrote:
> 
> > On Thu, Jan 13, 2011 at 4:11 PM, Stephen Hemminger
> >  <shemminger@vyatta.com> wrote:
> >  >
> > > It appears to be a different problem (not HPET MSI). Not sure  what
> > > is causing it, but even 2.6.35 can't format a floppy without  error.
> > 
> > Do you actually know that the hardware is good (ie does  _any_ version
> > of Linux work)?
> > 
> > Floppy disks and drives  have not been known for their robustness, and
> > most of them tend to be  pretty old by now.
> > 
> > Dang, I think I should just try to go to  Fry's and see if I can find a
> > floppy drive somewhere. Not that I even  know if my motherboards
> > necessarily even have the _pins_ to connect it  any more.
> > 
> >                           Linus
> 
> Some people can't even  remember what a floppy is...
>http://www.geek.com/articles/geek-pick/what-are-the-windows-a-and-b-drives-used-for-20110112/
>/


 you just made my day. Besides that I learned my computing on punched cards and 
tape (which may reveal something about my age) I really like the 5-core 
processing :-)

Happy weekend
Martin


  reply	other threads:[~2011-01-14 15:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 13:53 [GIT PULL] block driver updates for 2.6.38 Jens Axboe
2011-01-13 19:00 ` Linus Torvalds
2011-01-13 19:25   ` Jens Axboe
2011-01-13 19:40     ` Linus Torvalds
2011-01-13 21:43       ` Stephen Hemminger
2011-01-13 22:19       ` Stephen Hemminger
2011-01-14  0:02         ` Linus Torvalds
2011-01-14  0:11           ` Stephen Hemminger
2011-01-14  1:03             ` Linus Torvalds
2011-01-14  2:31               ` Stephen Hemminger
2011-01-14  4:53               ` Stephen Hemminger
2011-01-14  6:42               ` Stephen Hemminger
2011-01-14 15:55                 ` Martin Knoblauch [this message]
2011-01-20  2:01               ` Stephen Hemminger

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=940009.55868.qm@web113320.mail.gq1.yahoo.com \
    --to=spamtrap@knobisoft.de \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=penberg@kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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