public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "'Jiri Kosina'" <trivial@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kernel/itimer.c: beautify code, not need check 'value', so save one instruction, simpler and easier for readers.
Date: Fri, 21 Jun 2013 09:24:03 +0800	[thread overview]
Message-ID: <51C3AB33.6000901@asianux.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306201455330.4013@ionos.tec.linutronix.de>

On 06/20/2013 08:55 PM, Thomas Gleixner wrote:
> On Thu, 20 Jun 2013, Chen Gang wrote:
> 
>> > 
>> > Oh, sorry, maybe it is a trivial patch, also need send to
>> > trivial@kernel.org.
> No. This is not a trivial patch, it's changing the code flow.
>  

OK, that is not a trivial patch, but a minor patch, is it correct ??

;-)


Thanks.
-- 
Chen Gang

Asianux Corporation

  reply	other threads:[~2013-06-21  1:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 11:26 [PATCH v2] kernel/itimer.c: beautify code, not need check 'value', so save one instruction, simpler and easier for readers Chen Gang
2013-06-20 12:02 ` Chen Gang
2013-06-20 12:55   ` Thomas Gleixner
2013-06-21  1:24     ` Chen Gang [this message]
2013-06-20 13:42 ` Thomas Gleixner
2013-06-21  2:04   ` Chen Gang
2013-06-21 10:31     ` [PATCH v3] kernel/itimer.c: remove the checking 'value' statement Chen Gang
2013-06-24 23:28     ` [PATCH v2] kernel/itimer.c: beautify code, not need check 'value', so save one instruction, simpler and easier for readers.t Thomas Gleixner
2013-06-25  0:58       ` Chen Gang
2013-06-25  1:16         ` [PATH v4] itimers: Remove bogus NULL pointer check in sys_getitimer() Chen Gang
2013-07-05  1:28           ` Chen Gang
2013-07-22  2:45             ` Chen Gang

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=51C3AB33.6000901@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox