linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Matthew Garrett <mjg@redhat.com>, Liu Jiang <liuj97@gmail.com>,
	Dirk Griesbach <spamthis@freenet.de>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Liu Jiang <jiang.liu@huawei.com>
Subject: Re: [PATCH] libata: remove dead code from libata-acpi.c
Date: Fri, 21 Jun 2013 14:48:29 +0800	[thread overview]
Message-ID: <51C3F73D.3000603@intel.com> (raw)
In-Reply-To: <20130621062929.GB11014@mtj.dyndns.org>

On 06/21/2013 02:29 PM, Tejun Heo wrote:
> Hello,
> 
> On Fri, Jun 21, 2013 at 08:55:37AM +0800, Aaron Lu wrote:
>>>     Please indent this line under the next character after ( above.
>>
>> Is there a link about this rule? I might have missed something about
>> coding style.
> 
> I don't think there's an explicit rule about that and I don't follow
> it religiously but I think it does make things easier on the eyes and
> emacs does that by default so I just got used to it.  It's a very
> minor thing but FWIW I prefer things that way.

OK, will refresh the patch and send out again.

Thanks,
Aaron

  reply	other threads:[~2013-06-21  6:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  3:02 [PATCH] libata: remove dead code from libata-acpi.c Liu Jiang
2013-06-17  1:50 ` Aaron Lu
2013-06-17 18:01   ` Tejun Heo
2013-06-18  1:15     ` Jiang Liu (Gerry)
2013-06-18  9:16     ` Aaron Lu
2013-06-20  2:26       ` Aaron Lu
2013-06-20 11:02         ` Sergei Shtylyov
2013-06-21  0:55           ` Aaron Lu
2013-06-21  6:29             ` Tejun Heo
2013-06-21  6:48               ` Aaron Lu [this message]
2013-06-21 11:35             ` Sergei Shtylyov
2013-06-26  6:27               ` Aaron Lu
2013-06-21 15:25             ` James Bottomley
2013-06-26  2:01               ` Aaron Lu

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=51C3F73D.3000603@intel.com \
    --to=aaron.lu@intel.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuj97@gmail.com \
    --cc=mjg@redhat.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=spamthis@freenet.de \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).