From: Eugene Surovegin <ebs@ebshome.net>
To: emre kara <emrekara2002@yahoo.co.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PPC 440GX kernel 2.6 NAPI driver
Date: Fri, 18 Mar 2005 01:51:00 -0800 [thread overview]
Message-ID: <20050318095100.GC20239@gate.ebshome.net> (raw)
In-Reply-To: <20050318094143.34185.qmail@web25708.mail.ukl.yahoo.com>
On Fri, Mar 18, 2005 at 09:41:43AM +0000, emre kara wrote:
> but I can't patch the file for
> kernel 2.6.11 (emac_3-2.6-9.diff)(on kernel.org).
> Some .rej files created by patch.(ie mii.rej). Which
> kernel source must I use as base?
emac_3-2.6-9.diff is against 2.6 BK tree as of 2005-03-07 11:01pm PST.
I'll try to find some time this weekend and re-diff (if needed)
against latest BK, in the meantime, try resolving those rejects -
mii.rej shouldn't be very difficult.
If you applying patch to the 2.6.11 _release_ (not current BK tree),
try emac_3-2.6-8.diff.
--
Eugene
next prev parent reply other threads:[~2005-03-18 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 9:41 PPC 440GX kernel 2.6 NAPI driver emre kara
2005-03-18 9:51 ` Eugene Surovegin [this message]
2005-03-18 10:10 ` Eugene Surovegin
2005-03-18 10:14 ` Eugene Surovegin
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 10:25 emre kara
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=20050318095100.GC20239@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=emrekara2002@yahoo.co.uk \
--cc=linuxppc-embedded@ozlabs.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