Linux Container Development
 help / color / mirror / Atom feed
From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: anqin <anqin.qin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [PATCH] cgroup for disk quota
Date: Fri, 20 Feb 2009 17:44:07 +0100	[thread overview]
Message-ID: <499EDDD7.2030908@fr.ibm.com> (raw)
In-Reply-To: <d95d44a20902200830l1645e8b6j963f4ca62b5452f0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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
> linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org 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 linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org

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: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
	Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org

cf MAINTENERS file:

CONTROL GROUPS (CGROUPS)
P:      Paul Menage
M:      menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
L:      containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
S:      Maintained

Regards
   -- Daniel

      parent reply	other threads:[~2009-02-20 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  8:28 [PATCH] cgroup for disk quota anqin
     [not found] ` <d95d44a20902200028h1e229cc0pa3cdd4f42814e78e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 10:21   ` Fwd: " anqin
     [not found]     ` <d95d44a20902200221w67ee1b49ua6027f3090186af9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 10:32       ` Rolando Martins
     [not found]         ` <b6a2d2e20902200232x33204c61j30837a697d69c4d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 11:00           ` anqin
     [not found]             ` <d95d44a20902200300x43ef2ccfh6a66d3b81056d7fd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 13:51               ` Daniel Lezcano
     [not found]                 ` <499EB56B.6030502-GANU6spQydw@public.gmane.org>
2009-02-20 16:14                   ` anqin
2009-02-20 13:45   ` Daniel Lezcano
     [not found]     ` <499EB403.9050403-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2009-02-20 16:30       ` anqin
     [not found]         ` <d95d44a20902200830l1645e8b6j963f4ca62b5452f0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-20 16:44           ` Daniel Lezcano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499EDDD7.2030908@fr.ibm.com \
    --to=dlezcano-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
    --cc=anqin.qin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox