From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C update for 2.6.10-rc1
Date: Mon, 8 Nov 2004 21:24:17 -0800 [thread overview]
Message-ID: <10999778574012@kroah.com> (raw)
In-Reply-To: <1099977857196@kroah.com>
ChangeSet 1.2014.1.20, 2004/11/08 16:45:03-08:00, jthiessen@penguincomputing.com
[PATCH] I2C: fix lm85.c build warnings
Signed-off-by: Justin Thiessen <jthiessen@penguincomputing.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
drivers/i2c/chips/lm85.c | 32 --------------------------------
1 files changed, 32 deletions(-)
diff -Nru a/drivers/i2c/chips/lm85.c b/drivers/i2c/chips/lm85.c
--- a/drivers/i2c/chips/lm85.c 2004-11-08 18:54:44 -08:00
+++ b/drivers/i2c/chips/lm85.c 2004-11-08 18:54:44 -08:00
@@ -210,38 +210,6 @@
* MSB (bit 3, value 8). If the enable bit is 0, the encoded value
* is ignored, or set to 0.
*/
-static int lm85_smooth_map[] = { /* .1 sec */
- 350, 176, 118, 70, 44, 30, 16, 8
-/* 35.4 * 1/1, 1/2, 1/3, 1/5, 1/8, 1/12, 1/24, 1/48 */
- };
-static int SMOOTH_TO_REG( int smooth )
-{
- int i;
-
- if( smooth <= 0 ) { return 0 ; } /* Disabled */
- for( i = 0 ; i < 7 ; ++i )
- if( smooth >= lm85_smooth_map[i] )
- break ;
- return( (i & 0x07) | 0x08 );
-}
-#define SMOOTH_FROM_REG(val) ((val)&0x08?lm85_smooth_map[(val)&0x07]:0)
-
-/* These are the fan spinup delay time encodings */
-static int lm85_spinup_map[] = { /* .1 sec */
- 0, 1, 2, 4, 7, 10, 20, 40
- };
-static int SPINUP_TO_REG( int spinup )
-{
- int i;
-
- if( spinup >= lm85_spinup_map[7] ) { return 7 ; }
- for( i = 0 ; i < 7 ; ++i )
- if( spinup <= lm85_spinup_map[i] )
- break ;
- return( i & 0x07 );
-}
-#define SPINUP_FROM_REG(val) (lm85_spinup_map[(val)&0x07])
-
/* These are the PWM frequency encodings */
static int lm85_freq_map[] = { /* .1 Hz */
100, 150, 230, 300, 380, 470, 620, 940
next prev parent reply other threads:[~2004-11-09 5:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 5:22 [BK PATCH] I2C update for 2.6.10-rc1 Greg KH
2004-11-09 5:24 ` [PATCH] " Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH [this message]
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 5:24 ` Greg KH
2004-11-09 10:17 ` Jean Delvare
2004-11-09 11:12 ` Arjan van de Ven
2004-11-09 14:10 ` Jean Delvare
2004-11-09 9:29 ` [BK PATCH] " Jean Delvare
2004-11-09 15:21 ` Greg KH
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=10999778574012@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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