public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Patrick Boettcher <pboettcher@kernellabs.com>
Cc: linux-kernel@vger.kernel.org,
	Martin Habets <errandir_news@mph.eclipse.co.uk>
Subject: Re: PATCH [0/2] - CHECKSTACK: sparc-stack-size and formatting
Date: Mon, 23 Nov 2009 23:50:34 +0800	[thread overview]
Message-ID: <20091123155034.GF2412@hack> (raw)
In-Reply-To: <alpine.LRH.2.00.0911231148441.14263@pub1.ifh.de>

On Mon, Nov 23, 2009 at 12:01:00PM +0100, Patrick Boettcher wrote:
> Hi,
>
> I shamelessly stole the checkstack-script for a project of mine and now  
> want to contribute what I changed:
>
> 1) CHECKSTACK: sparc: fix regex to match all stacksizes

Please Cc sparc people for this, he should be David Miller, I think.


> 2) CHECKSTACK: simplify text-formatting for displaying the stacksize
>
> For 1): as there are no comments in the script as to why the regex was  
> limiting the detection of stacksizes to less 300 bytes and if I 
> understood it correctly, to a maximum of 1000, I simply removed it.

Please don't do this, write your change log for each patch please.


-- 
Live like a child, think like the god.
 

  parent reply	other threads:[~2009-11-23 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 11:01 PATCH [0/2] - CHECKSTACK: sparc-stack-size and formatting Patrick Boettcher
2009-11-23 11:04 ` PATCH [1/2] - CHECKSTACK: sparc: fix regex to match all stacksize Patrick Boettcher
2009-11-23 11:05 ` PATCH [2/2] - CHECKSTACK: simplify text-formatting for displaying the stacksize Patrick Boettcher
2009-11-23 15:50 ` Américo Wang [this message]
2009-11-30  1:09 ` PATCH [0/2] - CHECKSTACK: sparc-stack-size and formatting David Miller

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=20091123155034.GF2412@hack \
    --to=xiyou.wangcong@gmail.com \
    --cc=errandir_news@mph.eclipse.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pboettcher@kernellabs.com \
    /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