From: Armin <akuster@pacbell.net>
To: andrew may <acmay@acmay.homeip.net>
Cc: Matt Porter <mporter@mvista.com>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Status on 405GP i2c driver
Date: Wed, 24 Apr 2002 11:23:44 -0700 [thread overview]
Message-ID: <3CC6F830.807@pacbell.net> (raw)
In-Reply-To: 20020424083909.C17930@ecam.san.rr.com
andrew may wrote:
> On Wed, Apr 24, 2002 at 07:47:33AM -0700, Matt Porter wrote:
>
>>It's not a good idea to merge the i2c-2.6.3 support into 2_4_devel.
>>
>
> It seemed that Armins patch to the i2c list was against 2.6.3 so I deciede
> to merge that in before I merged in Armin's patch. I started doing the merge
> before you added in the files so that made things interesting. Unless you
> think 2.6.3 has some new bugs I see no reason to back out the changes in
> my tree.
>
Yes the patch sent to the i2c mailing list was against 2.6.3 since thats
their latest version. The *.c & *.h files should be the same in both trees
armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-24 18:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 21:16 Status on 405GP i2c driver andrew may
2002-04-23 17:54 ` Armin Kuster
2002-04-23 18:15 ` andrew may
2002-04-23 18:35 ` Armin Kuster
2002-04-23 19:14 ` andrew may
2002-04-23 23:05 ` Matt Porter
[not found] ` <20020423182301.B19665@ecam.san.rr.com>
2002-04-24 1:38 ` andrew may
2002-04-24 1:39 ` andrew may
2002-04-24 1:39 ` Status on 405GP i2c driver [PATCH] 2nd andrew may
2002-04-24 1:46 ` Status on 405GP i2c driver [PATCH] 3rd andrew may
2002-04-24 1:46 ` Status on 405GP i2c driver [PATCH] 4th andrew may
2002-04-24 1:47 ` Status on 405GP i2c driver [PATCH] last andrew may
2002-04-24 14:47 ` Status on 405GP i2c driver Matt Porter
2002-04-24 15:39 ` andrew may
2002-04-24 18:21 ` Matt Porter
2002-04-24 18:23 ` Armin [this message]
2002-04-25 8:04 ` file missing ? (was :Re: Status on 405GP i2c driver) "David Müller (ELSOFT AG)"
2002-04-25 14:36 ` Matt Porter
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=3CC6F830.807@pacbell.net \
--to=akuster@pacbell.net \
--cc=acmay@acmay.homeip.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mporter@mvista.com \
/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.