All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: steve@conceptoverdrive.com
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: SATA 2.4 ICH8
Date: Mon, 19 May 2008 22:26:25 +0200	[thread overview]
Message-ID: <20080519202625.GC5108@1wt.eu> (raw)
In-Reply-To: <48311942.8000407@sbcglobal.net>

Hi Steve,

On Sun, May 18, 2008 at 11:08:02PM -0700, Steve Rosenbluth wrote:
> Hello Willie,
> 
> Attached is the patch you asked for (ICH8 SATA controller definition).

OK thanks, I'm queueing it for 2.4.37.

> I have also supplied two other patches for 2.4.36.4
> 
> From the enclosed README :
> 
> "The following patches are for kernel 2.4.36.4 sources
> obtained from kernel.org :
> 
> intel_sata_ich8.patch
> This patches drivers/scsi/ata_piix.c
> It allows the kernel to access a SATA drive on an Intel ICH8 controller
> using the ich7 driver. This has been tested and it seems quite stable.
> 
> sigset_cast.patch
> This patches include/linux/signal.h
> There is an implicit cast from an integer to an
> unsigned long (sigset_t) which causes compilers to generate warnings.
> Different compilers could possibly produce different code.
> This change has been tested over several years of use and is stable.

OK, it makes sense. Another solution could have been to use ~0 instead of
(unsigned long)-1, but at least using -1 is easier to match with other
places. It would be kind to send the same patch for 2.6-mainline too.

> processor_colons_gcc-2.95.3.patch
> This patches include/asm/processor.h
> Sometime between 2.4.29 and 2.4.36.2 spaces were deleted between colons
> which causes compiler gcc 2.95.3 to fail to parse the header
> when compiling applications which include it.
> Adding back the spaces solves the problem on gcc 2.95.3.

Amusing. Interestingly, I mostly build my kernels with 2.95.3 too and never
got this funny thing. But I think that 2.95.3 has existed in so many flavors
that all we know is that it's based on some 2.95.[234] + more or less a ton
of patches.

> gcc 4.1.1 also compiles the kernel OK with this patch."

I have no worries about this :-)

OK, I'm queueing your patches.

Thanks Steve!
Willy


      reply	other threads:[~2008-05-19 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <480B925B.1080408@sbcglobal.net>
     [not found] ` <20080424221143.GB20775@1wt.eu>
2008-05-19  6:08   ` SATA 2.4 ICH8 Steve Rosenbluth
2008-05-19 20:26     ` Willy Tarreau [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=20080519202625.GC5108@1wt.eu \
    --to=w@1wt.eu \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=steve@conceptoverdrive.com \
    /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.