From: Ivo Manca <pinkel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Hans de Goede <j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 03/03] i2c-i801: Fix minor style issues
Date: Tue, 12 Aug 2008 22:50:55 +0200 [thread overview]
Message-ID: <48A1F7AF.4030707@gmail.com> (raw)
In-Reply-To: <20080812102711.6f8b178a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
> Looks OK, thanks for doing that.
>
Seemed to be the easiest and best way to shut checkpatch up ;)
> I'm now waiting for an update of your patches based on 2.6.27-rc2 for a
> final review.
>
I hope to have them finnished and sent tomorrow.
> Oh, one last note before I forget: as the interrupt-based logic is new
> and might not be as robust as the old poll-based one,
Likely
> it might make
> sense to give the user a way to disable the interrupt-based logic and
> fall back to polling in case the new code doesn't work correctly.
> Without that possibility, I won't feel too confident to push your
> patches to Linus. Remember that the ICH chips are very popular and we
> just can't afford breaking these systems.
>
True, i'd rather have that option as well.
> This could be implemented as a build time option enabling the new
> interrupt-based code, tagged EXPERIMENTAL and disabled by default, or a
> module parameter, or both.
>
What option do you think will generate more use and thus more testing? A
build time option (which is disabled by default thus won't be used by
the generic user) or a module parameter which people might not know the
existance of, but is easy to enable? Not sure what the best option is :).
> Thanks,
>
Ivo
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-08-12 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:57 [PATCH 03/03] i2c-i801: Fix minor style issues Ivo Manca
[not found] ` <48876301.9020903-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-12 8:27 ` Jean Delvare
[not found] ` <20080812102711.6f8b178a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-08-12 20:50 ` Ivo Manca [this message]
[not found] ` <48A1F7AF.4030707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-13 7:09 ` Jean Delvare
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=48A1F7AF.4030707@gmail.com \
--to=pinkel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=j.w.r.degoede-fbo2DhPpy/Q@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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.