From: Christophe Lucas <clucas@rotomalug.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] printk : kernel/softirq.c
Date: Fri, 07 Oct 2005 10:54:16 +0000 [thread overview]
Message-ID: <20051007105416.GC11049@titux.mcom.fr> (raw)
In-Reply-To: <03ca01c5cb00$c020f0f0$5f051aac@pcp42831>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Milind A Choudhary(Patni) (milind.choudhary@patni.com) wrote:
>
> Christophe Lucas [clucas@rotomalug.org] Wrote::
>
> >
> >Milind A Choudhary(Patni) (milind.choudhary@patni.com) wrote:
> >> Description:
> >> printk() calls should include appropriate KERN_* constant.
> >>
> >> Signed-off-by: Milind A Choudhary <milind.choudhary@patni.com>
> >
> >Hi,
> >
> >You seems to make printk patch. Have you made all patches for arch/i386
> >as you have begun ?
> >
> These are my first patches thats why i thougt
> doing some printk work would be a good startup..
> I've started looking into kernel/*
> haven't yet looked at arch/i386.
> are you planning to take it up?
No in a really next future.
>
> I'd like to know how do we,@ KJ, ensure that there is no repetition of work..
> is the work delegated or voluntarily taken up throgh such discussions only?
> kindly let me know.
As we do now : we ask on this ml :)
Have a nice day,
- Christophe (clucas@rotomalug.org)
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-10-07 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 5:46 [KJ] [PATCH] printk : kernel/softirq.c Milind A Choudhary(Patni)
2005-10-07 9:56 ` Christophe Lucas
2005-10-07 10:53 ` Milind A Choudhary(Patni)
2005-10-07 10:54 ` Christophe Lucas [this message]
2005-10-09 13:22 ` Arthur Othieno
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=20051007105416.GC11049@titux.mcom.fr \
--to=clucas@rotomalug.org \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.