Re: Designated initializers, struct randomization and addressing?

2017-01-03 Thread Bruce Korb
As a tangential party, I am a bit curious: does the randomization plugin result in a compact structure? I ask because I know many/most programmers don't bother with it and so doing so ought to make the data more compact. On Tue, Jan 3, 2017 at 3:47 PM, Kees Cook wrote: >> how is the code to be v

Re: [PATCH] staging: lustre: ldlm: use designated initializers

2016-12-20 Thread Bruce Korb
> > "{ NULL }" is valid ISO C, but unfortunately "{}" is not. Just make the thing "static const" and don't use an initializer.

Re: [PATCH] staging: lustre: ldlm: use designated initializers

2016-12-19 Thread Bruce Korb
On Mon, Dec 19, 2016 at 8:22 AM, James Simmons >> --- a/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c >> +++ b/drivers/staging/lustre/lustre/ldlm/ldlm_flock.c >> @@ -143,7 +143,7 @@ static int ldlm_process_flock_lock(struct ldlm_lock >> *req, __u64 *flags, >> int added = (mode == LCK_NL);

USB HID problem - more detail

2016-07-16 Thread Bruce Korb
*** My typing follows a line with a bunch of stars. That is followed by command output. *** The failing devices using usb-devices script have "no such file" errors: T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 27 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs=

USB HID problem

2016-07-16 Thread Bruce Korb
This is likely the wrong list, so I apologize in advance. Google didn't get me where I need to go. I have a USB 3.0 hub and switch that I need to use to switch devices between a Linux desktop, laptop and MacBook Pro. At first, I was testing with just a keyboard and mouse. The switch is connected

Re: [PATCH 05/15] staging: lustre: ldlm: use accessor macros for l_flags

2016-04-27 Thread Bruce Korb
On 04/27/16 15:20, James Simmons wrote: From: Bruce Korb Convert most of the ldlm lock's l_flags references from direct bit twiddling to using bit specific macros. A few multi-bit operations are left as an exercise for the reader. The changes are mostly in ldlm, but also in llite, osc

Re: Unknown PCI device?

2000-12-21 Thread Bruce Korb
"Mike A. Harris" wrote: > >> Anyone know what this is? > >> > >> 00:07.3 Host bridge: VIA Technologies, Inc.: Unknown device 3050 (rev 30) > >> Flags: medium devsel > > > >if its pci id is 0x11063050, then it's a VIA Power Management Controller. > > 00:07.3 Class 0600: 1106:3050 (rev 30)

Re: [patch] 2.2.18 PCI_DEVICE_ID_OXSEMI_16PCI954

2000-12-15 Thread Bruce Korb
Lukasz Trabinski wrote: > include/linux/pci_ids.h:#define PCI_DEVICE_ID_OXSEMI_16PCI954 0x9501 > > (IMHO that is correct), but in kernel 2.2.18 we have: > (include/kernel/pci.h) > #define PCI_DEVICE_ID_OXSEMI_16PCI954PP0x9513 > ^^ > > Please correct

Re: Linux 2.2.18 release notes

2000-12-12 Thread Bruce Korb
Peter Samuelson wrote: > > [AC] > > > ... added basic support for the Pentium IV. > [Android] > > How is the Pentium IV more advanced than the Pentium III, other than > > speed? Why would LInux care about a 1500 MHz clock or 400 MHz bus > > speed? Just treat the PIV as a faster PIII

Re: [PATCH] ide-pci.c: typo

2000-12-11 Thread Bruce Korb
Frédéric L . W . Meunier wrote: > > Alan Cox wrote: ... There are several typos, but it is not clear if they are all from ide-pci.c, or in the other files (pci.ids and pci_ids.h). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECT

Patch to improve PCI consistency

2000-12-10 Thread Bruce Korb
Hi, The information about PCI devices is scattered about the kernel and, consequently, is inconsistent. This patch puts the PCI/IDE bridge information into a text database along with the data from include/linux/pci_ids.h and drivers/pci/pci.ids. I may have mis- typed a few things, but the 2.4.