Re: after effects of a kernel API change

>
> Is there any way volunteers like me can help in this exercise?

See the /APIchanges in the Kernel Janitors TODO list
http://kernelnewbies.org/KernelJanitors/Todo


Hi,

This is regarding the link posted above.

1) How do I make sure if some one is NOT working on any of the
mentioned bullet points? Who coordinates? On what mailing list?

2) Do any patches for the above Todo list have the chances of getting
merged into the mainstream kernel? Who approves? I suppose the
respective maintainer of the driver / subsystem getting affected?

Thanks,

Rajat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: after effects of a kernel API change
  - From: "Ahmed S. Darwish" <[email protected]>
- Re: after effects of a kernel API change
  - From: [email protected] (Eric W. Biederman)

References:
- after effects of a kernel API change
  - From: "Daniel Rodrick" <[email protected]>
- Re: after effects of a kernel API change
  - From: "Ahmed S. Darwish" <[email protected]>

Prev by Date: Re: [RFC 0/8] Cpuset aware writeback
Next by Date: Re: query related to serial console
Previous by thread: Re: after effects of a kernel API change
Next by thread: Re: after effects of a kernel API change
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]