From: Tom Rini <trini@kernel.crashing.org>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Alan Cox <laughing@shared-source.org>,
Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c update to 2.6.0 for 2.4.7
Date: Wed, 25 Jul 2001 16:29:36 -0700 [thread overview]
Message-ID: <20010725162936.E4174@opus.bloom.county> (raw)
In-Reply-To: <20010725024629.E2308@werewolf.able.es> <20010724192805.A695@opus.bloom.county> <20010725105716.A6980@werewolf.able.es> <20010726012523.A1656@werewolf.able.es>
In-Reply-To: <20010726012523.A1656@werewolf.able.es>
On Thu, Jul 26, 2001 at 01:25:23AM +0200, J . A . Magallon wrote:
>
> On 20010725 J . A . Magallon wrote:
> >
> >On 20010725 Tom Rini wrote:
> >>On Wed, Jul 25, 2001 at 02:46:29AM +0200, J . A . Magallon wrote:
> >>> Hi.
> >>>
> >>> This patch updates i2c support in kernel to 2.6.0. I have corrected original patch
> >>> to use slab.h instead of malloc.h, a couple #endif's, and Comfigure.help references
> >>> to other docs in <file:...> format.
> >>
> >>It appears to be missing new files. The rpx and 405 bits aren't all there.
> >>
> >
> >Correct, the original patch generator skips them, both in 2.6.0 and latest cvs.
> >Why ?
> >Will redo the patch...
> >
>
> I have been looking at that part, and seems like pretty half-done, even buggy.
> Can't you live without it ?
The code actually works well, it just depends on other things which aren't yet
in Linus' tree but should be soon. There might be typos however.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2001-07-25 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 0:46 [PATCH] i2c update to 2.6.0 for 2.4.7 J . A . Magallon
2001-07-25 0:55 ` Steven Walter
2001-07-25 2:28 ` Tom Rini
2001-07-25 8:57 ` J . A . Magallon
2001-07-25 10:37 ` André Dahlqvist
2001-07-25 23:25 ` J . A . Magallon
2001-07-25 23:29 ` Tom Rini [this message]
2001-07-25 13:31 ` Alan Cox
2001-07-25 21:55 ` 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=20010725162936.E4174@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=jamagallon@able.es \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.