From: "J . A . Magallon" <jamagallon@able.es>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Linux 2.4.15-pre4 - merge with Alan
Date: Tue, 13 Nov 2001 01:42:48 +0100 [thread overview]
Message-ID: <20011113014248.A1487@werewolf.able.es> (raw)
In-Reply-To: <20011113004846.G1531@werewolf.able.es> <200111130014.fAD0Eel15650@ns.caldera.de>
In-Reply-To: <200111130014.fAD0Eel15650@ns.caldera.de>; from hch@ns.caldera.de on Tue, Nov 13, 2001 at 01:14:40 +0100
On 20011113 Christoph Hellwig wrote:
>In article <20011113004846.G1531@werewolf.able.es> you wrote:
>>
>> This is an update-cleanup of the i2c code to the current CVS. In short,
>> it adds version info printing and some CONFIG_ cleanups (there were
>> CONFIG_ vars defined in Config.in that had been renamed inside the code).
>> Please consider for next pre of 2.4.15.
>
>Could you please think before doing a merge next time?
>The patch backs out local changes like ite support:
>
>> -obj-$(CONFIG_I2C_ELEKTOR) += i2c-elektor.o
>> -obj-$(CONFIG_ITE_I2C_ALGO) += i2c-algo-ite.o
>> -obj-$(CONFIG_ITE_I2C_ADAP) += i2c-adap-ite.o
>> +obj-$(CONFIG_I2C_PCFISA) += i2c-elektor.o
>> obj-$(CONFIG_I2C_PROC) += i2c-proc.o
>
> Christoph
This should also stay, so ?
- if [ "$CONFIG_MIPS_ITE8172" = "y" ]; then
- dep_tristate 'ITE I2C Algorithm' CONFIG_ITE_I2C_ALGO $CONFIG_I2C
- if [ "$CONFIG_ITE_I2C_ALGO" != "n" ]; then
- dep_tristate ' ITE I2C Adapter' CONFIG_ITE_I2C_ADAP $CONFIG_ITE_I2C_ALGO
- fi
- fi
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.15-pre4-beo #2 SMP Tue Nov 13 00:50:12 CET 2001 i686
next prev parent reply other threads:[~2001-11-13 0:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 19:01 Linux 2.4.15-pre4 - merge with Alan Linus Torvalds
2001-11-12 19:18 ` Trever L. Adams
2001-11-13 11:14 ` Christoph Rohland
2001-11-12 19:26 ` Matthew Dharm
2001-11-12 20:09 ` Martin Dalecki
2001-11-12 20:42 ` Greg KH
2001-11-12 23:43 ` J . A . Magallon
2001-11-13 1:11 ` Alan Cox
2001-11-12 23:45 ` J . A . Magallon
2001-11-12 23:48 ` J . A . Magallon
2001-11-13 0:14 ` Christoph Hellwig
2001-11-13 0:25 ` J . A . Magallon
2001-11-13 0:42 ` J . A . Magallon [this message]
2001-11-13 7:43 ` Christoph Hellwig
2001-11-13 5:17 ` Keith Owens
2001-11-13 10:43 ` David S. Miller
2001-11-13 17:27 ` Chad N. Tindel
2001-11-13 17:58 ` Chad N. Tindel
2001-11-13 5:54 ` Neil Brown
2001-11-13 6:02 ` Jeff Garzik
2001-11-13 9:41 ` Alan Cox
2001-11-13 6:03 ` David S. Miller
2001-11-13 6:16 ` Keith Owens
2001-11-13 6:23 ` David S. Miller
2001-11-13 8:17 ` Jeff Garzik
2001-11-13 6:18 ` Keith Owens
2001-11-13 14:10 ` Horst von Brand
2001-11-13 15:21 ` Thorsten Kukuk
2001-11-14 4:57 ` David S. Miller
2001-11-14 6:28 ` Thorsten Kukuk
2001-11-14 6:31 ` David S. Miller
2001-11-14 12:59 ` Horst von Brand
2001-11-13 15:37 ` [PATCH] " Russell King
2001-11-15 9:25 ` Problem with Linux 2.4.15-pre4 on an IBM ThinkPad Martin Persson
2001-11-15 11:57 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 21:10 Linux 2.4.15-pre4 - merge with Alan Robert Cantu
2001-11-13 13:20 ` Andrey Savochkin
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=20011113014248.A1487@werewolf.able.es \
--to=jamagallon@able.es \
--cc=hch@ns.caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox