From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: Trouble with i2c and bttv
Date: Thu, 19 May 2005 06:24:04 +0000 [thread overview]
Message-ID: <3F0A2058.5040807@paradyne.com> (raw)
In-Reply-To: <200307042024.55272.tim.boneko@web.de>
What I mean is that we need to be prepared
to followup the i2c layer patch with the bttv fixup relatively quickly,
(you don't want the i2c patch to go in late in a release cycle either)
and the fixup may take some time, so in practice you may want to get started
on the fixup before you send in the i2c patch.
Jean Delvare wrote:
>>no, I think we need to send it all at once, it's a stable kernel
>
>
> I misexpressed myself. I mean we need to first have our patch (I2C layer
> + kernel drivers modifs) to be accepted before even having to help
> non-kernel modules (such as the zoran one which I'm using) convert their
> modules so that they will work with the new kernel.
>
> BTW, I need a new-I2C-layer patch for the kernel before I can change the
> zoran driver and test it. I guess that using our mkpatch script with
> I2C-cvs should do it?
>
> (This actually means that beginning with the zoran driver isn't the more
> logical thing to do, but since this is the only module I'll be able to
> test, better that way.)
>
prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 Trouble with i2c and bttv Tim Boneko
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker [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=3F0A2058.5040807@paradyne.com \
--to=mds@paradyne.com \
--cc=lm-sensors@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.