From: Matt Porter <mporter@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP List <linux-omap@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: gpmc-smsc911x: add required smsc911x regulators
Date: Wed, 22 Feb 2012 11:29:01 -0500 [thread overview]
Message-ID: <20120222162901.GB20411@beef> (raw)
In-Reply-To: <20120214110836.GE15338@n2100.arm.linux.org.uk>
On Tue, Feb 14, 2012 at 11:08:36AM +0000, Russell King - ARM Linux wrote:
> Two more points:
>
> On Mon, Feb 13, 2012 at 11:43:42AM -0500, Matt Porter wrote:
> > This fixes smsc911x support on platforms using gpmc_smsc911x_init().
> > Commit c7e963f6888816f04d1f5da0e07bec4e0092f227 added the requirement
>
> Always include the commit summary as well here, so:
>
> Commit c7e963f6888816 (net/smsc911x: Add regulator support) added the ...
Ok. Addressed in v2.
> > @@ -55,6 +94,11 @@ void __init gpmc_smsc911x_init(struct omap_smsc911x_platform_data *board_data)
> >
> > gpmc_cfg = board_data;
> >
> > + if (platform_device_register(&gpmc_smsc911x_regulator) < 0) {
> > + pr_err("Unable to register smsc911x regulators\n");
> > + return;
> > + }
>
> It's always a good idea to indicate why something failed:
>
> err = platform_device_register(&gpmc_smsc911x_regulator);
> if (err < 0) {
> pr_err("Unable to register smsc911x regulators: %d\n", err);
> return;
> }
>
> so that people can see not only what failed, but also why it failed.
Looks much better, also addressed in v2.
-Matt
WARNING: multiple messages have this Message-ID (diff)
From: mporter@ti.com (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: gpmc-smsc911x: add required smsc911x regulators
Date: Wed, 22 Feb 2012 11:29:01 -0500 [thread overview]
Message-ID: <20120222162901.GB20411@beef> (raw)
In-Reply-To: <20120214110836.GE15338@n2100.arm.linux.org.uk>
On Tue, Feb 14, 2012 at 11:08:36AM +0000, Russell King - ARM Linux wrote:
> Two more points:
>
> On Mon, Feb 13, 2012 at 11:43:42AM -0500, Matt Porter wrote:
> > This fixes smsc911x support on platforms using gpmc_smsc911x_init().
> > Commit c7e963f6888816f04d1f5da0e07bec4e0092f227 added the requirement
>
> Always include the commit summary as well here, so:
>
> Commit c7e963f6888816 (net/smsc911x: Add regulator support) added the ...
Ok. Addressed in v2.
> > @@ -55,6 +94,11 @@ void __init gpmc_smsc911x_init(struct omap_smsc911x_platform_data *board_data)
> >
> > gpmc_cfg = board_data;
> >
> > + if (platform_device_register(&gpmc_smsc911x_regulator) < 0) {
> > + pr_err("Unable to register smsc911x regulators\n");
> > + return;
> > + }
>
> It's always a good idea to indicate why something failed:
>
> err = platform_device_register(&gpmc_smsc911x_regulator);
> if (err < 0) {
> pr_err("Unable to register smsc911x regulators: %d\n", err);
> return;
> }
>
> so that people can see not only what failed, but also why it failed.
Looks much better, also addressed in v2.
-Matt
next prev parent reply other threads:[~2012-02-22 16:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 16:43 [PATCH] ARM: OMAP2+: gpmc-smsc911x: add required smsc911x regulators Matt Porter
2012-02-13 16:43 ` Matt Porter
2012-02-13 16:52 ` Russell King - ARM Linux
2012-02-13 16:52 ` Russell King - ARM Linux
2012-02-13 16:56 ` Mark Brown
2012-02-13 16:56 ` Mark Brown
2012-02-13 17:52 ` Tony Lindgren
2012-02-13 17:52 ` Tony Lindgren
2012-02-13 18:02 ` Russell King - ARM Linux
2012-02-13 18:02 ` Russell King - ARM Linux
2012-02-13 18:14 ` Tony Lindgren
2012-02-13 18:14 ` Tony Lindgren
2012-02-13 18:58 ` Mark Brown
2012-02-13 18:58 ` Mark Brown
2012-02-21 18:46 ` Tony Lindgren
2012-02-21 18:46 ` Tony Lindgren
2012-02-21 21:11 ` Matt Porter
2012-02-21 21:11 ` Matt Porter
2012-02-13 18:17 ` Matt Porter
2012-02-13 18:17 ` Matt Porter
2012-02-13 18:17 ` Matt Porter
2012-02-14 11:08 ` Russell King - ARM Linux
2012-02-14 11:08 ` Russell King - ARM Linux
2012-02-22 16:29 ` Matt Porter [this message]
2012-02-22 16:29 ` Matt Porter
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=20120222162901.GB20411@beef \
--to=mporter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/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.