From: Matt Domsch <Matt_Domsch@dell.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Meelis Roos <mroos@linux.ee>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-bk bogus edd changeset - Re: 2.4.23 compile error in edd
Date: Fri, 5 Dec 2003 12:53:51 -0600 [thread overview]
Message-ID: <20031205125351.A22277@lists.us.dell.com> (raw)
In-Reply-To: <20031205113619.A20371@lists.us.dell.com>; from Matt_Domsch@dell.com on Fri, Dec 05, 2003 at 11:36:19AM -0600
> Yeah, that's my bad, setup.c should say DISK80_SIG_BUFFER not
> DISKSIG_BUFFER.
BK patch to fix that:
Marcelo, please do a
bk pull http://mdomsch.bkbits.net/linux-2.4-edd
This will update the following files:
arch/i386/kernel/edd.c | 2 +-
arch/i386/kernel/setup.c | 2 +-
2 files changed, 2 insertions, 2 deletions
through these ChangeSets:
<Matt_Domsch@dell.com> (03/12/05 1.1199)
EDD: s/DISKSIG_BUFFER/DISK80_SIG_BUFFER so it compiles
bump EDD version number.
Tested on my PowerEdge 4600.
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2003-12-05 18:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 14:20 2.4.23 compile error in edd Meelis Roos
2003-12-04 14:58 ` Meelis Roos
2003-12-04 22:31 ` 2.4.23-bk bogus edd changeset - " Anton Altaparmakov
2003-12-05 15:52 ` Marcelo Tosatti
2003-12-05 17:36 ` Matt Domsch
2003-12-05 18:53 ` Matt Domsch [this message]
2003-12-05 19:07 ` Matt Domsch
2003-12-08 16:34 ` Anton Altaparmakov
2003-12-09 4:23 ` Matt Domsch
2003-12-09 16:29 ` Anton Altaparmakov
2003-12-10 20:48 ` Matt Domsch
2003-12-15 19:52 ` Anton Altaparmakov
2003-12-18 11:32 ` Meelis Roos
2003-12-18 14:02 ` Matt Domsch
2003-12-19 11:05 ` Meelis Roos
2003-12-19 14:49 ` Matt Domsch
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=20031205125351.A22277@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.