login
Header Space

 
 

Mailing list archives

Search results

Found 551 matching messages (0.022 seconds). Page 1 of 28.

Re: [RFC 1/2] labeled ipsec internet drafts

... label has the following format. > > 0 1 2 3 4 5 6 7 ... Association and Key > Management Protocol", RFC 2408, November 1998. > > [RFC2409] Harkins, ... Trust (2008). > > This document is subject to the rights, licenses and ...

linux-netdev - Paul Moore - Jul 26 2008 - 12:34

[PATCH/RFC 1/x] gitweb: Use git-diff-tree patch output for commitdiff

As the subject indicates (RFC), I'd like some comments on that patch. This patch is ... @gmail.com> --- gitweb/gitweb.perl | 323 ++++++++++++++++++++++++++++++++-------------------- 1 files changed, 201 insertions(+), 122 deletions(-) ...

git - Jakub Narebski - Aug 23 2006 - 18:15

[RFC 1/1][PATCH] POSIX SCHED_SPORADIC implementation for tasks and groups

... its runqueue. It's an RFC, but it is fully working, ... Issue 6", IEEE Std 1003.1, + 2004 Edition. + + [http://www.opengroup. ... ss->low_priority); + __enqueue_rt_entity(rt_se); + } + + return 1; + } + + return 0; +} + +static inline void ...

linux-kernel - Dario Faggioli - Aug 11 2008 - 10:45

[PATCH RFC 1/6] Docs: send-email's usage text and man page mention same options

... due to SMTP limits as described by http://www.ietf.org/rfc/rfc2821.txt. +-- + --to:: Specify the primary recipient of the emails ... quiet Make git-send-email less verbose. One line per email -- 1.6.0.2.302.ge6cbd1 -- To unsubscribe from this ...

git - Michael Witten - Sep 22 2008 - 11:58

[PATCH RFC 1/6] Docs: send-email's usage text and man page mention same options

... due to SMTP limits as described by http://www.ietf.org/rfc/rfc2821.txt. +-- + --to:: Specify the primary recipient of the emails ... quiet Make git-send-email less verbose. One line per email -- 1.6.0.2.302.ge6cbd1 -- To unsubscribe from this ...

git - Michael Witten - Sep 25 2008 - 16:44

Subject: [RFC 1/1] cpumask: Provide new cpumask API

... () for idiotically small > values. > > Linus Subject: [RFC 1/1] cpumask: Provide new cpumask API ... local variable */ typedef struct __cpumask_data_s cpumask_var_t[1]; /* SMALL NR_CPUS */ typedef struct __cpumask_data_s *cpumask_var_t; ...

linux-kernel - Mike Travis - Sep 25 2008 - 16:59

[RFC 1/28] Pass struct vfsmount to the inode_create LSM hook.

Pass struct vfsmount to the inode_create LSM hook. Signed-off-by: Tony Jones Signed-off-by: Andreas Gruenbacher Index: linux-2.6/fs/namei.c =================================================================== ---

linux-kernel - Tony Jones - Feb 5 2007 - 14:22

Re: [RFC 1/2] Input: ff, add FF_RAW effect

On 4/18/07, Jiri Slaby wrote: > johann deneux napsal(a): > > Jiri, > > > > Which solution did you chose to implement? From what I remember, we > > last discussed Dmitry's idea of specifying an axis for an effect, then > >

linux-kernel - johann deneux - Apr 19 2007 - 00:25

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Hi, On Thursday 19 April 2007 00:25, johann deneux wrote: > On 4/18/07, Jiri Slaby wrote: > > johann deneux napsal(a): > > > Jiri, > > > > > > Which solution did you chose to implement? From what I remember, we > > > last

linux-kernel - Dmitry Torokhov - Apr 19 2007 - 00:58

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Jiri, Which solution did you chose to implement? From what I remember, we last discussed Dmitry's idea of specifying an axis for an effect, then combine several effects to achieve complex effects. The implementation would specify the axis using the

linux-kernel - johann deneux - Apr 18 2007 - 16:00

Re: [RFC 1/2] Input: ff, add FF_RAW effect

johann deneux napsal(a): > Jiri, > > Which solution did you chose to implement? From what I remember, we > last discussed Dmitry's idea of specifying an axis for an effect, then > combine several effects to achieve complex effects. I think you

linux-kernel - Jiri Slaby - Apr 18 2007 - 17:07

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Dmitry Torokhov napsal(a): > I have been thinking about this and I don't think that exporting motor > data is a good idea, at least not in case of Phantom driver. The fact > that there are 3 motors is a hardware implementation detail and it > is not

linux-kernel - Jiri Slaby - Apr 19 2007 - 11:38

Re: [RFC 1/2] Input: ff, add FF_RAW effect

On 4/19/07, Jiri Slaby wrote: > Dmitry Torokhov napsal(a): > > I have been thinking about this and I don't think that exporting motor > > data is a good idea, at least not in case of Phantom driver. The fact > > that there are 3

linux-kernel - Dmitry Torokhov - Apr 19 2007 - 12:02

Re: [RFC 1/2] Input: ff, add FF_RAW effect

On 4/19/07, Dmitry Torokhov wrote: > On 4/19/07, Jiri Slaby wrote: > > Dmitry Torokhov napsal(a): > > > If we are interested in using FF API we need to come up with a way > > > to express this effect

linux-kernel - Jiri Slaby - Apr 22 2007 - 08:57

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Dmitry Torokhov napsal(a): > For devices that require tailored application (for example that glove > - I am not sure how a generic application could control it) old > phantom way of controlling via ioctl will suffice. The device may > still use input

linux-kernel - Jiri Slaby - Apr 23 2007 - 15:30

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Hi Jiri, On 4/23/07, Jiri Slaby wrote: > Dmitry Torokhov napsal(a): > > For devices that require tailored application (for example that glove > > - I am not sure how a generic application could control it) old > > phantom way

linux-kernel - Dmitry Torokhov - Apr 26 2007 - 11:58

Re: [RFC 1/2] Input: ff, add FF_RAW effect

On 4/22/07, Jiri Slaby wrote: > On 4/19/07, Dmitry Torokhov wrote: > > On 4/19/07, Jiri Slaby wrote: > > > Dmitry Torokhov napsal(a): > > > > If we are interested in using FF API

linux-kernel - Dmitry Torokhov - Apr 26 2007 - 12:02

Re: [RFC 1/2] Input: ff, add FF_RAW effect

Dmitry Torokhov napsal(a): > On 4/22/07, Jiri Slaby wrote: >> I think we won't be able to make the transition in independent way >> due to unspecified meaning of the torques. >> > > With phantom it still seems doable - if I

linux-kernel - Jiri Slaby - Apr 26 2007 - 19:24

Re: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors

On Sat, 5 May 2007, Pekka Enberg wrote: > For consistency with other operations structures, can we make this > struct kmem_cache_operations or kmem_cache_ops, please? Ok. - To unsubscribe from this list: send the line "unsubscribe linux-kernel

linux-kernel - Christoph Lameter - May 5 2007 - 11:43

Re: [RFC 1/3] SLUB: slab_ops instead of constructors / destructors

On 5/5/07, clameter@sgi.com wrote: > This patch gets rid constructors and destructors and replaces them > with a slab operations structure that is passed into SLUB. Looks good to me. On 5/5/07, clameter@sgi.com

linux-kernel - Pekka Enberg - May 5 2007 - 06:14

speck-geostationary