public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Rudmer van Dijk <rudmer@legolas.dynup.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, andre@linux-ide.org
Subject: Re: Linux 2.5.14-dj2
Date: Sat, 11 May 2002 21:36:30 +0200	[thread overview]
Message-ID: <20020511213630.A30904@suse.de> (raw)
In-Reply-To: <4.1.20020511114723.009c8270@pop.cablewanadoo.nl> <20020508225147.GA11390@suse.de> <4.1.20020511114723.009c8270@pop.cablewanadoo.nl> <20020511191406.S5262@suse.de> <4.1.20020511205025.009703a0@pop.cablewanadoo.nl>

On Sat, May 11, 2002 at 09:04:20PM +0200, Rudmer van Dijk wrote:
 > >http://linus.bkbits.net:8080/linux-2.5/cset@1.513.1.14?nav=index.html
 > and still the patch I included applied to 2.5.14-dj2... 

*boggle* $deity knows how.
I just checked. From a clean 2.4.14, with -dj2 patch applied, that
segment of code reads..

#if SUPPORT_SLOW_DATA_PORTS
        if (drive->channel->slow)
            ata_write_slow(drive, buffer, wcount);
        else
#endif 
            ata_write_16(drive, buffer, wcount);
    }

So this part..

 > > > - 			ata_write_16(drive, buffer, wcount<<1);
 > > > + 			ata_write_16(drive, buffer, wcount);

Should reject (or at least say already applied)

It may be patch(1) being funky, and doing something silly like adding the
same patch twice (something thats bitten me a few times, and has also happened
in Linus' tree once or twice).

        Dave.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

      reply	other threads:[~2002-05-11 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-08 22:51 Linux 2.5.14-dj2 Dave Jones
2002-05-09  9:46 ` Adrian Bunk
2002-05-09 14:33   ` Dave Jones
2002-05-11 14:46 ` Rudmer van Dijk
2002-05-11 15:00   ` Tomas Szepe
2002-05-11 17:14   ` Dave Jones
2002-05-11 19:04     ` Rudmer van Dijk
2002-05-11 19:36       ` Dave Jones [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=20020511213630.A30904@suse.de \
    --to=davej@suse.de \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rudmer@legolas.dynup.net \
    /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