Whoops, sorry, this is of course titled RFC 3/3. On Mon, 28 Apr 2008 21:58:54 +0300 Pekka Paalanen #define PF_RSVD (1<<3) > #define PF_INSTR (1<<4) > > +static inline int kmmio_fault(struct ...

linux-kernel - Pekka Paalanen - Apr 28 2008 - 15:02

... ->cpus bits. That means we > never mwait after a kick. > Yeah, I have to admit I never tested this code (it was an RFC, after all). And after Arjan said that mwait is unusable, I didn't spend any more effort on it. > See: > > >> +void ...

linux-kernel - Jeremy Fitzhardinge - Aug 28 2008 - 13:33

... " (not just this) ... + */ +static unsigned dw_dmac0_data = 3; + +static struct resource dw_dmac0_resource[] = { + PBMEM(0xff200000), ... 1 +#define DMAC_DAC_TX 2 +#define DMAC_AC97_A_RX 3 +#define DMAC_AC97_A_TX 4 +#define DMAC_AC97_B_RX 5 +# ...

linux-kernel - Haavard Skinnemoen - Nov 23 2007 - 08:20

... by: "Theodore Ts'o" --- scripts/setlocalversion | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git ... ; then printf '%s' -dirty fi fi -- 1.5.3.4.499.g1104e-dirty - To unsubscribe from this list: send ...

linux-kernel - Theodore Ts'o - Nov 2 2007 - 21:53

... arch/avr32/mm/init.c | 3 +-- arch/ia64/mm/discontig.c | ... i = 0; ; i++) { @@ -340,5 +340,3 @@ unsigned long omapfb_reserve_sram(unsign #endif - ... #ifndef CONFIG_DISCONTIGMEM @@ -252,4 +251,3 @@ void free_initrd_mem(unsigned long start ...

linux-kernel - Johannes Weiner - May 20 2008 - 21:37

... doesn't make sense with preempt disabled 3. vmx_cpu_run doesn't handle error correctly ... 't make sense with preempt disabled 3. vmx_cpu_run doesn't handle error correctly ... 't make sense with preempt disabled 3. vmx_cpu_run doesn't handle error correctly ...

linux-kernel - Shaohua Li - Jul 23 2007 - 02:51

... 17:58 +0200, Laurent Vivier wrote: >> [PATCH 3/3] introduce "account modifiers" mechanism in the ... asks. It is very generic. - remove PATCH 3, and add in task_struct a "ktime ... modify PATCH 4 to use new PATCH 3. Do you agree ? Anybody doesn't agree ...

linux-kernel - Laurent Vivier - Aug 17 2007 - 03:35

... :11 -0500 > Dean Nelson wrote: > > > > > 3) WARNING: declaring multiple variables together should be avoided > ... > What warning does it generate here? The WARNING #3 above "declaring multiple variables together should be avoided". ...

linux-kernel - Dean Nelson - Aug 22 2007 - 15:15

... > > Dean Nelson wrote: > > > > > > > > 3) WARNING: declaring multiple variables together should be avoided > ... > What warning does it generate here? > > The WARNING #3 above "declaring multiple variables together should be avoided" ...

linux-kernel - Andrew Morton - Aug 22 2007 - 15:49

... -0500 >>> Dean Nelson wrote: >>> >>>> 3) WARNING: declaring multiple variables together should be avoided >>>> ... >>> What warning does it generate here? >> The WARNING #3 above "declaring multiple variables together should be avoided". ...

linux-kernel - Andy Whitcroft - Aug 23 2007 - 09:58

... setup_git_directory(); git_config(git_default_config); - if (argc < 3 || argc > 4) + + for (i = 1; ... value = argv[2]; - oldval = argv[3]; if (get_sha1(value, sha1)) die("% ... return 1; return 0; } -- 1.3.2.g7278 - To unsubscribe from ...

git - Shawn Pearce - May 17 2006 - 05:55

... on x86, as well as on s390. 3. An additional stage is also needed due to the ... This effect is in some way similar to #3, but can (and did) happen even when there ... famous last words). I will rerun with GP_STAGES==3 on POWER to double-check -- it is ...

linux-kernel - Paul E. McKenney - Sep 21 2007 - 18:06

... understanding of why we fail with 3 stages and not 4. > Perhaps you ... : I continue running the GP_STAGES=3 run on the pair of POWER ... number is, assuming it is neither 3 nor 4, and figure out why ... -lp1 machine choked on GP_STAGES=3. Then we can work out ...

linux-kernel - Paul E. McKenney - Sep 22 2007 - 00:07

... Jeremy Fitzhardinge wrote: > > > >> +#define PAGETABLE_LEVELS 3 > >> + > >> +typedef u64 pteval_t; > >> +typedef u64 pmdval_t; > >> + ... paravirt.h, just split out between the < 3 and >= 3 levels. But if it turns out to ...

linux-kernel - Glauber de Oliveira Costa - Nov 8 2007 - 18:38

... )) continue; - fputs(line, stderr); + set_ref_error(refs, line + 3); ret = -1; } return ret; @@ -258,6 +278,12 @@ ... renaming */ char name[FLEX_ARRAY]; /* more */ }; -- 1.5.3.5.1704.g24d42-dirty - To unsubscribe from this list: ...

git - Jeff King - Nov 13 2007 - 06:29

... /moxa.c | 16 +++++++++++++--- 1 files changed, 13 insertions(+), 3 deletions(-) diff --git a/drivers/char/moxa.c b/drivers/ ... 2); } static struct pci_driver moxa_pci_driver = { -- 1.5.3.7 -- To unsubscribe from this list: send the line " ...

linux-kernel - Jiri Slaby - Jan 24 2008 - 05:32

... space is provided through +"as_limit_in_bytes". The file is similar to "limit_in_bytes" w.r.t the user +interface. Please see section 3 for more details on how to use the user +interface to get and set values. + +The "as_usage_in_bytes" file provides ...

linux-kernel - Balbir Singh - Mar 16 2008 - 13:30

... to "limit_in_bytes" w.r.t the user w.r.t. or even spelled out. > +interface. Please see section 3 for more details on how to use the user > +interface to get and set values. > + > ...

linux-kernel - Randy Dunlap - Mar 16 2008 - 14:32

... > > w.r.t. > or even spelled out. > Will spell out. >> +interface. Please see section 3 for more details on how to use the user >> +interface to get and set values. >> + >> + ...

linux-kernel - Balbir Singh - Mar 16 2008 - 21:33

... is provided through +"as_limit_in_bytes". The file is similar to "limit_in_bytes" w.r.t. the user +interface. Please see section 3 for more details on how to use the user +interface to get and set values. + +The "as_usage_in_bytes" file provides ...

linux-kernel - Balbir Singh - Mar 26 2008 - 14:50