anqin wrote:
>>> BTW, I don't know how to submit a "useful" patch to kernel community. Or,
>>> maybe the patch is not useful at all and maybe has been developed by other
>>> developers. I very appreciate if both of experts could give me some
>>> commend.
>>> I will continue to develop cgroup-related codes to make contribution to
>>> kernel
>>> development.
>> I am not sure I understand what you mean by "useful", but it seems you did
>> an interesting feature. All the documentation related to submitting patches
>> is in Documentation/SubmittingPatches, I hope that helps.
>>
>
> I learn from some kernel developers that they said only useful patches will be
> accepted by community and applied on next kernel mainstream version.
> So, I don't know whether or not my patch can be seen as "useful" by
> most of users while it is developed under my project requirements.
>
>
>> send your patches to lkml@ prefixed with [RFC] in the subject ('quilt' is
>> your friend). If the functionality already exists, someone will tell you.
>>
>
> mmh... SubmittingPatches said patches should be sent to
> [email protected] if there is not "MAINTAINERS file",
> after fixed into standard style. what are different with that
> you have said? The " lkml@ prefixed " seems not be mentioned
> in SubmittingPatches, what should I do?
lkml@ = linux kernel mailing list aka [email protected]
I think you will find the answers of all your questions here:
http://kernelnewbies.org/UpstreamMerge
If you are looking for the recipients of your patches, IMO you should send:
To: Paul Menage
Cc: [email protected]
Cc: [email protected]
cf MAINTENERS file:
CONTROL GROUPS (CGROUPS)
P: Paul Menage
M: [email protected]
L: [email protected]
S: Maintained
Regards
-- Daniel
_______________________________________________
Containers mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Devel mailing list
[email protected]
https://openvz.org/mailman/listinfo/devel
