From: Aaron Lu <aaron.lu@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Tejun Heo <tj@kernel.org>, 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: Wed, 26 Jun 2013 10:01:56 +0800 [thread overview]
Message-ID: <51CA4B94.3040008@intel.com> (raw)
In-Reply-To: <1371828346.3040.3.camel@dabdike>
On 06/21/2013 11:25 PM, James Bottomley wrote:
> On Fri, 2013-06-21 at 08:55 +0800, Aaron Lu wrote:
>> On 06/20/2013 07:02 PM, Sergei Shtylyov wrote:
>>> Hello.
>>
>> Hi,
>>
>> Thanks for your comments.
>>
>>>
>>> On 20-06-2013 6:26, Aaron Lu wrote:
>>>>
>>>> +void ata_acpi_hotplug_init(struct ata_host *host)
>>>> +{
>>>> + int i;
>>>> +
>>>> + for (i = 0; i < host->n_ports; i++) {
>>>> + struct ata_port *ap = host->ports[i];
>>>> + acpi_handle handle;
>>>> + struct ata_device *dev;
>>>> +
>>>> + if (!ap)
>>>> + continue;
>>>> +
>>>> + handle = ata_ap_acpi_handle(ap);
>>>> + if (handle) {
>>>> + /* we might be on a docking station */
>>>> + register_hotplug_dock_device(handle,
>>>> + &ata_acpi_ap_dock_ops, ap);
>>>
>>> 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.
>
> The rule is follow the coding style in the file, unless there's
> something really wrong with it (which there might be in the case of
> really old drivers). The reason is that a mixture of coding styles
> makes the file much harder to read than a single consistent style.
Oh right, that's the rule I missed. Thanks for letting me know.
>
> In this case, if you look at libata-acpi.c you see all continuation
> lines of function calls are aligned with open braces.
Indeed.
-Aaron
prev parent reply other threads:[~2013-06-26 2:01 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
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 [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=51CA4B94.3040008@intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@HansenPartnership.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