public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: John Mylchreest <johnm@gentoo.org>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org, paulus@samba.org
Subject: Re: [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16
Date: Sun, 2 Apr 2006 10:58:50 +0200	[thread overview]
Message-ID: <20060402085850.GA28857@suse.de> (raw)
In-Reply-To: <20060401224849.GH16917@getafix.willow.local>

 On Sat, Apr 01, John Mylchreest wrote:

> Since ppc32 has been made to use arch/powerpc it has introduced a build-time
> regression where userland CFLAGS are being leaked. This is especially obvious
> when a user tries to "make zImage" with an SSP enabled gcc.

What build error do you get?

  reply	other threads:[~2006-04-02  8:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01 22:48 [PATCH 1/1] POWERPC: Fix ppc32 compile with gcc+SSP in 2.6.16 John Mylchreest
2006-04-02  8:58 ` Olaf Hering [this message]
2006-04-02 10:22   ` John Mylchreest
2006-04-02 10:28     ` Olaf Hering
2006-04-02 10:58       ` John Mylchreest
2006-04-02 11:10         ` Olaf Hering
2006-04-02 11:20           ` John Mylchreest
2006-04-02 11:42             ` Olaf Hering
2006-04-04  8:57               ` John Mylchreest
2006-04-04  9:41                 ` Olaf Hering
2006-04-04 10:01                   ` John Mylchreest
2006-04-04 10:58                     ` Olaf Hering
2006-04-10  9:01                       ` John Mylchreest
2006-04-02 13:15             ` Arjan van de Ven
2006-04-02 13:56               ` John Mylchreest
2006-04-02 14:01                 ` Olaf Hering
2006-04-02 14:35                   ` John Mylchreest
2006-04-02 14:49                 ` Arjan van de Ven
2006-04-02 15:22                   ` John Mylchreest

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=20060402085850.GA28857@suse.de \
    --to=olh@suse.de \
    --cc=johnm@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=stable@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