public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Anton Vorontsov <anton@enomsg.org>
Cc: jason.wessel@windriver.com, sasha.levin@oracle.com,
	vincent.stehle@laposte.net, john.blackwood@ccur.com,
	kgdb-bugreport@lists.sourceforge.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/debug/kdb: code enhancement for 3 areas.
Date: Tue, 28 May 2013 14:07:12 +0800	[thread overview]
Message-ID: <51A44990.5010109@asianux.com> (raw)
In-Reply-To: <519EBFD2.60105@asianux.com>

On 05/24/2013 09:18 AM, Chen Gang wrote:
> On 05/24/2013 01:28 AM, Anton Vorontsov wrote:
>> > On Thu, May 16, 2013 at 07:25:46PM +0800, Chen Gang wrote:
>>>> >> > Delete waste '{' for 'case' statement.
>>>> >> > 
>>>> >> > For the return variable 'long res' in function kdb_task_state_string(),
>>>> >> > neither it matches the function return type 'unsigned long', nor is
>>>> >> > suitable as a flag variable to make 'or' operation. So use 'unsigned
>>>> >> > long' instead of 'long'.
>>>> >> > 
>>>> >> > If "case 'A'" happen in function kdb_task_state_string(), can return
>>>> >> > ~0UL directly to save the useless looping.
>>>> >> > 
>>>> >> > Signed-off-by: Chen Gang <gang.chen@asianux.com>
>> > If anything, these should be 3 separate patches...
>> > 

My original 3 fix issues old patches for "kernel/debug" are still
non-reply, then the new minor cleanup patches (if I will provide the 3
patches) will of cause be none-reply, too.

Now, I am not a newbie anymore, so I can/should understand it, at least,
it should not stop me to continue providing patches to another members.

And thank you for your encouraging.

:-)


> OK, I will separate them into 3 patches (originally, I think for trivial
> cleanup patches, better let them in one patch, so can save the reviewers
> and appliers time)
> 
> Excuse me, I have to do something else, so I will finish them within
> this month (2013-05-31)
> 
> 
> Thanks.
> -- Chen Gang Asianux Corporation


-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-05-28  6:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 11:25 [PATCH] kernel/debug/kdb: code enhancement for 3 areas Chen Gang
2013-05-23 17:28 ` Anton Vorontsov
2013-05-24  1:18   ` Chen Gang
2013-05-28  6:07     ` Chen Gang [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=51A44990.5010109@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=anton@enomsg.org \
    --cc=jason.wessel@windriver.com \
    --cc=john.blackwood@ccur.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=vincent.stehle@laposte.net \
    /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