All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include/linux/platform_data: beautify code, 'inline' is better in front of 'void'
Date: Tue, 26 Mar 2013 11:00:40 +0800	[thread overview]
Message-ID: <51510F58.70602@asianux.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1303252246540.1372@syhkavp.arg>

On 2013年03月26日 10:47, Nicolas Pitre wrote:
> On Tue, 26 Mar 2013, Chen Gang wrote:
> 
>>   a hacker may find something "valuable" with the aid of compiler   ;-)
>>
>>   maybe, it is a patch which is too minor to apply. I can understand :-)
> 
> You should send such patches to Jiri Kosina <trivial@kernel.org>.
> 

  ok

> 
> Nicolas
> 
> 


-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-03-26  3:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  2:36 [PATCH] include/linux/platform_data: beautify code, 'inline' is better in front of 'void' Chen Gang
2013-03-25  2:48 ` [Suggestion] scripts/checkpatch.pl: an issue about checking failed for a patch Chen Gang
2013-03-25 23:32 ` [PATCH] include/linux/platform_data: beautify code, 'inline' is better in front of 'void' Greg KH
2013-03-26  1:22   ` Chen Gang
2013-03-26  1:48     ` Greg KH
2013-03-26  2:28       ` Chen Gang
2013-03-26  2:47         ` Nicolas Pitre
2013-03-26  3:00           ` 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=51510F58.70602@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=arnd@arndb.de \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=nicolas.pitre@linaro.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.