From: Ben Lau <benlau@linux.org.hk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Simon Oosthoek <simon@cal003100.student.utwente.nl>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre5
Date: Fri, 28 Feb 2003 13:46:16 +0800 [thread overview]
Message-ID: <3E5EF7A8.8050307@linux.org.hk> (raw)
In-Reply-To: <1046342924.27186.249.camel@zion.wanadoo.fr>
Hi,
Is there any simple method to trace which patch removed
the code?
I used the following command to check it..
grep define\ *hpsb_queue_struct\ *tq_struct patch-2.4.21-pre4-ac*
However, i have downloaded the patch from alan cox only...
it dont contain the code. any site have contained all the
patches that is -pre5 based on?
Benjamin Herrenschmidt wrote:
> On Thu, 2003-02-27 at 11:19, Simon Oosthoek wrote:
>
>
>>here's a patch that should work to fix this.
>
>
> I think the proper fix for now is to bring back all of
> ieee1394 from pre4 to pre5, it was an incorrect merge
> that reverted part of it.
>
> Ben.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-02-28 5:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 6:14 Linux 2.4.21-pre5 Marcelo Tosatti
2003-02-27 8:24 ` Christoph Hellwig
2003-02-27 8:32 ` Adrian Bunk
2003-02-27 12:40 ` Ben Collins
2003-02-27 19:22 ` ajoshi
2003-02-27 19:35 ` Ben Collins
2003-03-11 23:39 ` Marcelo Tosatti
2003-02-27 8:53 ` Christoph Hellwig
2003-02-27 9:39 ` Ben Lau
2003-02-27 10:19 ` Simon Oosthoek
2003-02-27 10:48 ` Benjamin Herrenschmidt
2003-02-27 11:43 ` Simon Oosthoek
2003-02-28 5:46 ` Ben Lau [this message]
2003-02-27 23:26 ` [patch] 2.4.21-pre5: fix Auerswald compile Adrian Bunk
2003-02-28 7:47 ` Wolfgang Mües
2003-03-05 22:02 ` Greg KH
2003-03-07 2:47 ` Linux 2.4.21-pre5 J.A. Magallon
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=3E5EF7A8.8050307@linux.org.hk \
--to=benlau@linux.org.hk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@cal003100.student.utwente.nl \
/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