From: Jim Nelson <james4765@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH 00/72] arm: add KERN_ constants to files in
Date: Fri, 08 Sep 2006 03:24:48 +0000 [thread overview]
Message-ID: <4500E280.5080903@gmail.com> (raw)
In-Reply-To: <20060908015622.10114.66478.sendpatchset@david.homenet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matthew Wilcox wrote:
> On Thu, Sep 07, 2006 at 09:56:22PM -0400, James Nelson wrote:
>> This series of patches add appropriate KERN_ constants to printk()s in the rest of
>> the files in /arch/arm. It also reworks some debug #defines to make their operation
>> more clear.
>
> Posting a 72 part series is completely unreasonable. Never do this again.
> Find a better way of splitting it up -- maybe by directory. One patch
> per file is ridiculous.
You are right. I will have to re-work the script I use to package everything up
- - I haven't done this much work in one shot before...
My apologies.
Jim
- --
GPG key available
gpg --keyserver pgp.mit.edu --recv-keys 06B386612
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFFAOJ/XxNjpms4ZhIRAuzDAJ9ZYntb/iC9JmnZYnmZo//Kp42HiACgoxt7
i/1/+lgUTU6VUX5vT9h8uyk=m9cx
-----END PGP SIGNATURE-----
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-09-08 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 1:56 [KJ] [PATCH 00/72] arm: add KERN_ constants to files in arch/arm/* James Nelson
2006-09-08 2:29 ` [KJ] [PATCH 00/72] arm: add KERN_ constants to files in Matthew Wilcox
2006-09-08 3:24 ` Jim Nelson [this message]
2006-09-08 7:08 ` Russell King
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=4500E280.5080903@gmail.com \
--to=james4765@gmail.com \
--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.