public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Tom Rini <trini@kernel.crashing.org>,
	"J . A . Magallon" <jamagallon@able.es>,
	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: Thu, 26 Jul 2001 01:25:23 +0200	[thread overview]
Message-ID: <20010726012523.A1656@werewolf.able.es> (raw)
In-Reply-To: <20010725024629.E2308@werewolf.able.es> <20010724192805.A695@opus.bloom.county> <20010725105716.A6980@werewolf.able.es>
In-Reply-To: <20010725105716.A6980@werewolf.able.es>; from jamagallon@able.es on Wed, Jul 25, 2001 at 10:57:16 +0200


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 ?

For example, in mkpatch/Config.in:

   if [ "$CONFIG_8xx" = "y" ]; then
<well, there is a 8xx cpu variable in arch/ppc>
...
   if [ "$CONFIG_405" = "y" ]; then
<I found no _405, should not it be _4xx ?>
      dep_tristate 'PPC 405 I2C Algorithm' CONFIG_I2C_PPC405_ALGO $CONFIG_I2C
                               look at this ^^^^^^^^^^^^^^^^^^^^
      if [ "CONFIG_PPC405_I2C_ALGO" != "n" ]; then
     <vs this ^^^^^^^^^^^^^^^^^^^^ >
         dep_tristate '  PPC 405 I2C Adapter' CONFIG_I2C_PPC405_ADAP $CONFIG_I2C
_PPC405_ALGO

I would not trust that part still.

BTW, I sent the patches about slab/malloc to the mantainer time ago, and cvs
still uses malloc. 

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.1 (Cooker) for i586
Linux werewolf 2.4.7 #1 SMP Mon Jul 23 01:55:36 CEST 2001 i686

  parent reply	other threads:[~2001-07-25 23:21 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 [this message]
2001-07-25 23:29       ` Tom Rini
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=20010726012523.A1656@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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