mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Melnikoff <temnota+news@kmv.ru>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2.4.31 1/1] scsi/megaraid2: add 64-bit application sup?port
Date: Wed, 3 Aug 2005 14:44:16 +0400	[thread overview]
Message-ID: <0pj6s2-grt.ln1@kenga.kmv.ru> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5703662A89@exa-atlanta>

Ju, Seokmann <sju@lsil.com> wrote:
> [-- text/plain, encoding 7bit, charset: iso-8859-1, 1346 lines --]

> Hi Marcelo,

> I've made changes that reflect your comments.

> On Tuesday, July 26, 2005 4:33 AM, Marcelo Tosatti wrote:
> > vary_io has never been part of mainline. How come did you add it
> > here?
> Has removed '.vary_io'.
> > There is no CONFIG_COMPAT on v2.4... thanks James and Christoph
> > for reviewing.
> Has removed 'CONFIG_COMPAT'.

> Thank you.

> Signed-off-by: Seokmann Ju <seokmann.ju@lsil.com>
Still not compile with gcc-3.4

-- cut --
gcc-3.4 -D__KERNEL__ -I/usr/src/linux-2.4.31/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-fno-unit-at-a-time   -nostdinc -iwithprefix include
-DKBUILD_BASENAME=megaraid2  -c -o megaraid2.o megaraid2.c
megaraid2.c: In function `megaraid_queue':
megaraid2.h:1113: sorry, unimplemented: inlining failed in call to
'mega_runpendq': function body not available
megaraid2.c:1033: sorry, unimplemented: called from here
megaraid2.c: In function `mega_n_to_m':
megaraid2.c:4658: warning: unused variable `uiocp'
make[3]: *** [megaraid2.o] Error 1

-- cut --


  reply	other threads:[~2005-08-03 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02 20:29 [PATCH 2.4.31 1/1] scsi/megaraid2: add 64-bit application sup port Ju, Seokmann
2005-08-03 10:44 ` Andrey Melnikoff [this message]
2005-08-04 21:09 [PATCH 2.4.31 1/1] scsi/megaraid2: add 64-bit application sup ?port Ju, Seokmann

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=0pj6s2-grt.ln1@kenga.kmv.ru \
    --to=temnota+news@kmv.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®