From: Luc Saillard <luc@saillard.org>
To: Norbert Preining <preining@logic.at>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pwc driver in -mm kernels
Date: Tue, 29 Mar 2005 10:52:58 +0200 [thread overview]
Message-ID: <20050329085257.GA18799@sd291.sivit.org> (raw)
In-Reply-To: <20050321150954.GD14614@gamma.logic.tuwien.ac.at>
On Mon, Mar 21, 2005 at 04:09:54PM +0100, Norbert Preining wrote:
> On Mon, 21 Mär 2005, Alan Cox wrote:
> > I pushed the tested one as a starting point. May have been the wrong
> > decision but it's my fault if so
>
> Ah ok. I checked the differences between the versions but there are too
> many `none-standard' changes, i.e. kernel-language changes (statics,
> inlines, __) etc so that I cannot submit a patch for the new version.
>
> The good thing about the one on Luc's page it that it includes sysfs
> support for several parameters and some more device ids.
Sorry, i was in holliday far far away from my computer (it's very rare).
I can produce a patch with coding style fixes, or wait to fix a bug in v4l2
then submit the patch. What do you prefer ? Some applications crashes when
using the v4l2 API. I can made v4l2 optional.
I know that a lot of changes needs to be applied to the driver to please
everybody. So perhaps i can try to begin with a patch (with v4l2), and wait
for feedback, and resend patch until this is correct ?
Luc
prev parent reply other threads:[~2005-03-29 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 13:04 Norbert Preining
2005-03-19 21:00 ` Greg KH
2005-03-21 14:56 ` Alan Cox
2005-03-21 15:09 ` Norbert Preining
2005-03-29 8:52 ` Luc Saillard [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=20050329085257.GA18799@sd291.sivit.org \
--to=luc@saillard.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
/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
all inboxes | Powered by JetHome®