linux-kernel - Re: linux-next: Tree for January 22 (staging/android)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4978F968.7010108@oracle.com>
Date:	Thu, 22 Jan 2009 14:55:36 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Greg KH <gregkh@...e.de>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for January 22 (staging/android)

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 */
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/