From: "J.A. Magallon" <jamagallon@able.es>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make i2c use initcalls everywhere
Date: Sun, 29 Dec 2002 23:26:28 +0100 [thread overview]
Message-ID: <20021229222628.GC2259@werewolf.able.es> (raw)
In-Reply-To: <20021229220436.A11420@lst.de>; from hch@lst.de on Sun, Dec 29, 2002 at 22:04:36 +0100
On 2002.12.29 Christoph Hellwig wrote:
> The use of explicit initializers all over the i2c core anoyed for
> long, but the lm_sensors merge with two new files just for initializers
> was too much. Conver all of i2c to sane initialization (mostly
> initcall, but some driver also got other cleanups in that area)
>
Wil this reach the i2c maintainer or the next auto-generated patch from i2c
2.8.x will undo what you do now and will be sized 4Gb ?
Will i2c ever get in sync into 2.4 ? Nowadays the main of the patch is a ton
of 'stupid' changes from printk(xxx) to I2C_DEBUG(xxx) or the like.
Will this be accepted if I submit it, even independently of the maintainer ?
Because I suppose (???) that maintainer is sending changes and they are going
to trash...
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre2-jam2 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk))
next prev parent reply other threads:[~2002-12-29 22:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 21:04 [PATCH] make i2c use initcalls everywhere Christoph Hellwig
2002-12-29 22:26 ` J.A. Magallon [this message]
2002-12-29 22:37 ` Christoph Hellwig
2002-12-29 22:53 ` J.A. Magallon
2002-12-29 23:19 ` Andrew Walrond
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=20021229222628.GC2259@werewolf.able.es \
--to=jamagallon@able.es \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox