All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH 00/72] arm: add KERN_ constants to files in
Date: Fri, 08 Sep 2006 07:08:06 +0000	[thread overview]
Message-ID: <20060908070806.GA9039@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060908015622.10114.66478.sendpatchset@david.homenet>

On Thu, Sep 07, 2006 at 11:24:48PM -0400, Jim Nelson wrote:
> 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...

I also don't understand why you've sent several series of almost one patch
per file for ARM.

Please do as Matthew suggests - I won't be applying these as is.  Thanks.

-- 
Russell King
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

      parent reply	other threads:[~2006-09-08  7:08 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
2006-09-08  7:08 ` Russell King [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=20060908070806.GA9039@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --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.