linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mikpe@csd.uu.se
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: mikpe@csd.uu.se, Kaj-Michael Lang <milang@tal.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	linuxppc-dev@lists.linuxppc.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre7
Date: Wed, 9 Apr 2003 12:20:24 +0200	[thread overview]
Message-ID: <16019.62440.828553.117381@gargle.gargle.HOWL> (raw)
In-Reply-To: <1049882960.559.35.camel@zion.wanadoo.fr>

Benjamin Herrenschmidt writes:
 > On Wed, 2003-04-09 at 11:55, mikpe@csd.uu.se wrote:
 > > Kaj-Michael Lang writes:
 > >  > > So here goes -pre7. Hopefully the last -pre.
 > >  > >
 > >  > Won't compile for my PPC:
 > >  > ---
 > >  >         -o vmlinux
 > >  > drivers/ide/idedriver.o(.text+0x1a544): In function `pmac_outbsync':
 > >  > : undefined reference to `io_flush'
 > >  > drivers/ide/idedriver.o(.text+0x1a544): In function `pmac_outbsync':
 > >  > : relocation truncated to fit: R_PPC_REL24 io_flush
 > > 
 > > Someone updated pmac.c without testing it: io_flush() doesn't exist
 > > in 2.4.21-pre. Based on the diff from -pre6 to -pre7, I'd say the
 > > following is a reasonable approximation. My PM4400 runs with this
 > > patch right now.
 > 
 > Or just get my devel rsync.
 > 
 > Actually, what happened is that Marcelo took the version that was
 > in -ac tree, which I sent to Alan a while ago and is now outdated.
 > The io_flush macro was something I added to the arch includes and
 > later removed as I fixed the problem differently.
 > 
 > Marcelo: I sent you a fixed version, please do not apply this patch
 > but rather the one I sent you.

Ok, I can understand what happened, but shouldn't these fixes be
cc:d to or at last announced on LKML as well? It could be a month
before Marcelo does a -pre8 or -rc1.

  reply	other threads:[~2003-04-09 10:09 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 21:15 Linux 2.4.21-pre7 Marcelo Tosatti
2003-04-04 21:34 ` J.A. Magallon
2003-04-04 21:01   ` Alan Cox
2003-04-04 22:44 ` kernel
2003-04-05  0:31 ` J.A. Magallon
2003-04-05 16:55   ` Alan Cox
2003-04-05  0:43 ` J.A. Magallon
2003-04-05  0:50   ` [PATCH] AT_PLATFORM on HT-P4 J.A. Magallon
2003-04-05  1:18     ` Benjamin LaHaise
2003-04-05  1:22       ` J.A. Magallon
2003-04-05  1:24         ` Benjamin LaHaise
2003-04-05  0:50   ` [PATCH] redundant printk decl J.A. Magallon
2003-04-05  0:52   ` [PATCH] thread signaling J.A. Magallon
2003-04-05 16:53     ` Alan Cox
2003-04-05  0:53   ` [PATCH] detached clone J.A. Magallon
2003-04-05  0:55   ` [PATCH] e1000 close J.A. Magallon
2003-04-05  2:06   ` Linux 2.4.21-pre7 Marcelo Tosatti
2003-04-05  0:51 ` Nathan Poznick
2003-04-05  3:52 ` Linux 2.4.21-pre7 - hpt366.c does not build Eyal Lebedinsky
2003-04-21 16:33   ` Marcelo Tosatti
2003-04-05 16:03 ` Linux 2.4.21-pre7 Udo A. Steinberg
2003-04-05 21:49 ` Jerome Chantelauze
2003-04-05 22:42 ` J.A. Magallon
2003-04-05 23:02   ` [PATCH] AT_PLATFORM on HT-P4 J.A. Magallon
2003-04-05 23:03   ` Linux 2.4.21-pre7 J.A. Magallon
2003-04-05 23:06   ` [PATCH] config/dep bugs J.A. Magallon
2003-04-06 22:18     ` Karl Weigel
2003-04-05 23:08   ` [PATCH] thread signaling J.A. Magallon
2003-04-05 23:09   ` [PATCH] detached cloning J.A. Magallon
2003-04-07 23:13     ` Daniel Jacobowitz
2003-04-09 23:29       ` J.A. Magallon
2003-04-10 15:12         ` Daniel Jacobowitz
2003-04-05 23:12   ` [PATCH] e1000 close J.A. Magallon
2003-04-06 14:53     ` Alan Cox
2003-04-08 16:28 ` Linux 2.4.21-pre7 Kaj-Michael Lang
2003-04-09  9:55   ` mikpe
2003-04-09 10:09     ` Benjamin Herrenschmidt
2003-04-09 10:20       ` mikpe [this message]
2003-04-09 11:01         ` Benjamin Herrenschmidt
2003-04-09 14:27         ` Ruth Ivimey-Cook

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=16019.62440.828553.117381@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=marcelo@conectiva.com.br \
    --cc=milang@tal.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;
as well as URLs for NNTP newsgroup(s).