public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IBM Thinkpad A21 BIOS - EDD information wrong
Date: Sat, 11 Oct 2003 10:30:24 -0700	[thread overview]
Message-ID: <20031011173024.GC22274@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0310102143550.5365-100000@iguana.domsch.com>

On Fri, Oct 10, 2003 at 09:46:05PM -0500, Matt Domsch wrote:
> > > /sys/firmware/edd/int13_dev80/raw_data
> > Hm, I thought you were going to use the sysfs binary file interface for
> > this file, instead of outputing a hex dump.  Any reason for keeping it
> > this way?
> 
> Laziness?  No really, it just slipped my mind.  I've got the read-disk-sig 
> patch I'm working on related to EDD again, so I'll fix it right soon.  
> Would that fit under Linus's 'bug-only' policy?

I would say yes, as it's a bug that the current code is implementing a
hex dump in kernel space :)

thanks,

greg k-h

      reply	other threads:[~2003-10-11 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 21:39 IBM Thinkpad A21 BIOS - EDD information wrong Matt_Domsch
2003-10-10 23:56 ` Greg KH
2003-10-11  2:46   ` Matt Domsch
2003-10-11 17:30     ` Greg KH [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=20031011173024.GC22274@kroah.com \
    --to=greg@kroah.com \
    --cc=Matt_Domsch@dell.com \
    --cc=linux-kernel@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