public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.7-dj3
Date: Thu, 04 Apr 2002 13:41:21 +0200	[thread overview]
Message-ID: <3CAC3BE1.9030300@evision-ventures.com> (raw)
In-Reply-To: <20020404054923.A28437@suse.de> <Pine.NEB.4.44.0204040946500.7845-100000@mimas.fachschaften.tu-muenchen.de> <20020404141647.T20040@suse.de> <20020404143722.V20040@suse.de>

Dave Jones wrote:
> On Thu, Apr 04, 2002 at 02:16:47PM +0200, Dave Jones wrote:
>  > On Thu, Apr 04, 2002 at 09:50:32AM +0200, Adrian Bunk wrote:
>  >  > pdc4030.c: In function `promise_multwrite':
>  >  > pdc4030.c:447: warning: passing arg 2 of `bio_kmap_irq' makes pointer from
>  >  > integer without a cast
>  >  > pdc4030.c: In function `promise_rw_disk':
>  >  > pdc4030.c:664: structure has no member named `channel'
>  > 
>  > Ok, I'm confused.
>  > This is a compile failure from 2.5.8-pre1.
>  > The line numbers don't even match up to whats in -dj3
> 
> 
> My bad. _I_ was looking at a wrong tree.
> I'll fix these bits up later and push them Martins way, as there
> are a few other small IDE bits that have been lingering in my
> tree since 2.5.2 days.

Well actually I was short before having a look in to the -dj3 series,
but first I have to read through 2.5.8-pre1.
However I would be really gald if you could throw the code in question
in fragments called patches at me ;-).


  reply	other threads:[~2002-04-04 12:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04  5:49 Linux 2.5.7-dj3 Dave Jones
2002-04-04  7:50 ` Adrian Bunk
2002-04-04 12:16   ` Dave Jones
2002-04-04 12:37     ` Dave Jones
2002-04-04 11:41       ` Martin Dalecki [this message]
2002-04-04 15:22 ` Linux 2.5.7-dj3 - BUG & PATCH Sebastian Droege
2002-04-04 17:54   ` Greg KH
2002-04-04 18:01     ` Dave Jones
2002-04-05  6:45   ` Greg KH
2002-04-05  9:48     ` Sebastian Droege

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=3CAC3BE1.9030300@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=davej@suse.de \
    --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