From: Marek Vasut <marek.vasut@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-fbdev-devel@lists.sourceforge.net, lm-sensors@lm-sensors.org
Subject: Re: build issue #7 for v2.6.30-rc3 :defined but not
Date: Thu, 23 Apr 2009 20:11:28 +0200 [thread overview]
Message-ID: <200904232011.28308.marek.vasut@gmail.com> (raw)
In-Reply-To: <200904232001.21042.toralf.foerster@gmx.de>
On Thursday 23 of April 2009 20:01:20 Toralf Förster wrote:
> include/linux/ucb1400.h:139: warning: 'ucb1400_adc_read' defined but not
> used
include/linux/ucb1400.h:139: warning: 'ucb1400_adc_read' defined but not used
That function should probably go into ucb1400-core.c
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-fbdev-devel@lists.sourceforge.net, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] build issue #7 for v2.6.30-rc3 :defined but not
Date: Thu, 23 Apr 2009 18:11:28 +0000 [thread overview]
Message-ID: <200904232011.28308.marek.vasut@gmail.com> (raw)
In-Reply-To: <200904232001.21042.toralf.foerster@gmx.de>
On Thursday 23 of April 2009 20:01:20 Toralf Förster wrote:
> include/linux/ucb1400.h:139: warning: 'ucb1400_adc_read' defined but not
> used
include/linux/ucb1400.h:139: warning: 'ucb1400_adc_read' defined but not used
That function should probably go into ucb1400-core.c
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-04-23 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 18:01 build issue #7 for v2.6.30-rc3 :defined but not Toralf Förster
2009-04-23 18:11 ` Marek Vasut [this message]
2009-04-23 18:11 ` [lm-sensors] " Marek Vasut
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=200904232011.28308.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=lm-sensors@lm-sensors.org \
--cc=toralf.foerster@gmx.de \
/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.