All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] Support for Barco LTP->DVI parport I2C
Date: Wed, 23 Nov 2005 22:28:26 +0000	[thread overview]
Message-ID: <20051123222910.107c1bee.khali@linux-fr.org> (raw)
In-Reply-To: <87oe4d4uit.fsf@48ers.dk>

Hi Peter,

>  Jean> Is there any reason why someone outside of Barco would use that
>  Jean> interface and driver?
> 
> Realistically no. I could provide the schematics and someone could
> make their own prints, but as all of the parport boards are pretty
> much the same anyway, it doesn't really have any advantages compared
> to the one in Documentation/i2c/busses/i2c-parport.
> 
> The reason why I would like it included is simply that it doesn't
> harm anyone and it would make it easier for us since it's used by
> several people - some without much Linux mojo, so having it in the
> mainline kernel would be nice instead of having to patch the kernels.

OK, fair enough, I was thinking quite the same. The overhead is indeed
so thin it's not even worth arguing about.

>  Jean> May I have a Barco device for free, just to test the driver? :)
>  Jean> Just kidding...
> 
> I'll see what I can do..

Come on, I was *really* kidding :) You don't even need to try and
corrupt me, your patch is already accepted as far as I am concerned.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2005-11-23 22:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 21:26 [lm-sensors] [PATCH] Support for Barco LTP->DVI parport I2C adapter Peter Korsgaard
2005-11-22 21:42 ` [lm-sensors] [PATCH] Support for Barco LTP->DVI parport I2C Jean Delvare
2005-11-22 21:54 ` Peter Korsgaard
2005-11-23 12:45 ` Jean Delvare
2005-11-23 21:37 ` Peter Korsgaard
2005-11-23 22:28 ` Jean Delvare [this message]
2005-11-24  7:03 ` Peter Korsgaard

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=20051123222910.107c1bee.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.