From: Tom Rini <trini@kernel.crashing.org>
To: Stephen Williams <612dlag102@sneakemail.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Head of linuxppc-2.4 broekn by davem patch
Date: Fri, 11 Jun 2004 14:40:54 -0700 [thread overview]
Message-ID: <20040611214054.GB925@smtp.west.cox.net> (raw)
In-Reply-To: <29963-82182@sneakemail.com>
On Fri, Jun 11, 2004 at 09:07:13AM -0700, Stephen Williams wrote:
> Stefan Nickl Stefan.Nickl-at-kontron.com |PPC Linux Embedded| wrote:
> >I already sent this patch to the list and to "davem" who
> >commited the faulty version, but nobody seems to care...
>
> Here is the exact same patch, packaged slightly differently
> and re-sent, just in case it got lost in someone's inbox.
> It is also possible that davem is thinking in terms of
> changing the sk_buff definition t match this file. Either
> way, something must be done.
I've gotten around to updating the linuxppc-2.4 repository to match the
current state of linux-2.4 again. If there's still a problem, I would
suggest reproducing it with an i386 config (or CONFIG_ALL_PPC config)
and posting to lkml (linux-kernel@vger.kernel.org) and cc'ing Marcelo
and whomever made the broken change. The problem in question didn't
come from us PPC folks, so fixing it in our tree is, IMHO, pointless
(the fix will either become obsolete and introduce minor pain when a fix
comes in upstream or the change will be reverted, again probably causing
us pain merging this in).
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-11 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1086934906.4820.2.camel@lucy.pep-kaufbeuren.de>
2004-06-11 16:07 ` Head of linuxppc-2.4 broekn by davem patch Stephen Williams
2004-06-11 21:40 ` Tom Rini [this message]
2004-06-11 22:01 ` Stephen Williams
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=20040611214054.GB925@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=612dlag102@sneakemail.com \
--cc=linuxppc-embedded@lists.linuxppc.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).