From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <gregkh@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for January 22 (staging/android)
Date: Thu, 22 Jan 2009 14:55:36 -0800 [thread overview]
Message-ID: <4978F968.7010108@oracle.com> (raw)
In-Reply-To: <20090122221849.GA30477@suse.de>
Greg KH wrote:
> On Thu, Jan 22, 2009 at 09:16:00AM -0800, Randy Dunlap wrote:
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20090121:
>> drivers/staging/android/timed_gpio.c: In function 'gpio_enable_show':
>> drivers/staging/android/timed_gpio.c:52: error: 'ktime_t' has no member named 'tv'
>> drivers/staging/android/timed_gpio.c:52: error: 'ktime_t' has no member named 'tv'
>
> Is this due to a change in -next? I see 'tv' as a valid field in
> kime_t in Linus's tree.
>
> confused,
>
> greg k-h
'tv' is a union name, not a field name, right?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=include/linux/ktime.h;h=ce5983225be4e6430cadbff9cc5cbf448a66e647;hb=HEAD :
46 union ktime {
47 s64 tv64;
48 #if BITS_PER_LONG != 64 && !defined(CONFIG_KTIME_SCALAR)
49 struct {
50 # ifdef __BIG_ENDIAN
51 s32 sec, nsec;
52 # else
53 s32 nsec, sec;
54 # endif
55 } tv;
56 #endif
57 };
58
59 typedef union ktime ktime_t; /* Kill this */
next prev parent reply other threads:[~2009-01-22 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 7:05 linux-next: Tree for January 22 Stephen Rothwell
2009-01-22 17:14 ` linux-next: Tree for January 22 (staging/rtl8187se) Randy Dunlap
2009-01-22 17:18 ` Randy Dunlap
2009-01-22 17:18 ` Randy Dunlap
2009-01-22 17:21 ` Randy Dunlap
2009-01-22 17:14 ` linux-next: Tree for January 22 (staging/altpcichdma) Randy Dunlap
2009-01-22 17:16 ` linux-next: Tree for January 22 (staging/android) Randy Dunlap
2009-01-22 22:18 ` Greg KH
2009-01-22 22:55 ` Randy Dunlap [this message]
2009-01-23 9:54 ` Rebooting at boot: linux-next: Tree for January 22 Nico -telmich- Schottelius
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=4978F968.7010108@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.