From: James Bottomley <James.Bottomley@steeleye.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.5.70-mm2: NCR_D700.c doesn't compile
Date: 29 May 2003 17:01:56 -0400 [thread overview]
Message-ID: <1054242118.1819.465.camel@mulgrave> (raw)
In-Reply-To: <20030529205742.GI5643@fs.tum.de>
On Thu, 2003-05-29 at 16:57, Adrian Bunk wrote:
> It seems the following compile error comes from Linus' tree:
Yes, I already have the fix (which is to add the correct argument to the
function).
James
next prev parent reply other threads:[~2003-05-29 20:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 8:29 2.5.70-mm2 Andrew Morton
2003-05-29 8:29 ` 2.5.70-mm2 Andrew Morton
2003-05-29 8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 8:49 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-29 11:23 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:05 ` 2.5.70-mm2 John Stoffel
2003-05-30 20:05 ` 2.5.70-mm2 John Stoffel
2003-05-30 20:30 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:30 ` 2.5.70-mm2 Andrew Morton
2003-05-30 20:56 ` 2.5.70-mm2 John Stoffel
2003-05-30 20:56 ` 2.5.70-mm2 John Stoffel
2003-05-30 22:36 ` 2.5.70-mm2 Mingming Cao
2003-05-30 22:36 ` 2.5.70-mm2 Mingming Cao
2003-05-29 12:55 ` 2.5.70-mm2 still dies with RAID-1 Helge Hafting
2003-05-29 12:55 ` Helge Hafting
2003-05-29 19:40 ` [patch] 2.5.70-mm2: aha1740.c doesn't compile Adrian Bunk
2003-05-29 20:57 ` 2.5.70-mm2: NCR_D700.c " Adrian Bunk
2003-05-29 21:01 ` James Bottomley [this message]
2003-05-29 21:17 ` 2.5.70-mm2: NCR53C9x.c " Adrian Bunk
2003-05-29 21:52 ` 2.5.70-mm2 Badari Pulavarty
2003-05-30 11:17 ` 2.5.70-mm2 Andrew Morton
2003-05-30 11:17 ` 2.5.70-mm2 Andrew Morton
2003-05-29 22:15 ` 2.5.70-mm2: g_NCR5380 link errors Adrian Bunk
2003-05-30 8:05 ` [patch] 2.5.70-mm2: `__raw_{read,write}ll' undefinded references Adrian Bunk
2003-05-30 8:05 ` Adrian Bunk
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=1054242118.1819.465.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@digeo.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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.