From: Andrew Walrond <andrew@walrond.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make i2c use initcalls everywhere
Date: Sun, 29 Dec 2002 23:19:43 +0000 [thread overview]
Message-ID: <3E0F830F.9040203@walrond.org> (raw)
In-Reply-To: 20021229225350.GE2259@werewolf.able.es
Agreed. I would love to see the i2c and lmsensor stuff properly
maintained in the kernel tree; It would save a whole lot of dicking around.
Pretty please? ;)
J.A. Magallon wrote:
> On 2002.12.29 Christoph Hellwig wrote:
>
>>On Sun, Dec 29, 2002 at 11:26:28PM +0100, J.A. Magallon wrote:
>>
>>>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 ?
>>
>>There is no maintainer for drivers/i2c/. The only updates it every got
>>was me syncinc with their releases and backing out obvious braindamage.
>>
>>
>>>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...
>>
>>Maybe the changes the maintainers of the external i2c code are sending
>>_are_ trash?
>>
>
>
> (just put on the flame war suit...)
>
> Stupid question: why people on http://secure.netroedge.com/~lm78/ is not
> smashed with a hammer on the head and 'morally forced' to post, comment, etc.
> patches on LKML ? They continue to ship releases, every vendor tracks them,
> and every vendor has to correct changes they have not tracked from mainline,
> like that old about __exit functions, and now initcalls...
>
> I really do not understand some things about Linux. Some people look like
> living in alternative universes...
>
prev parent reply other threads:[~2002-12-29 23:11 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
2002-12-29 22:37 ` Christoph Hellwig
2002-12-29 22:53 ` J.A. Magallon
2002-12-29 23:19 ` Andrew Walrond [this message]
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=3E0F830F.9040203@walrond.org \
--to=andrew@walrond.org \
--cc=hch@infradead.org \
--cc=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 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.