From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Gopinath, Thara" <thara@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Menon, Nishanth" <nm@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Peter p2 De Schrijver <peter.de-schrijver@nokia.com>
Subject: RE: [PATCH 2/2] omap3: sr: improve errors handling
Date: Fri, 09 Jul 2010 18:44:05 +0300 [thread overview]
Message-ID: <1278690245.9953.142.camel@localhost> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB032391F34E@dbde02.ent.ti.com>
On Fri, 2010-07-09 at 20:35 +0530, Gopinath, Thara wrote:
>
> >>-----Original Message-----
> >>From: Artem Bityutskiy [mailto:dedekind1@gmail.com]
> >>Sent: Friday, July 09, 2010 6:50 PM
> >>To: linux-omap@vger.kernel.org
> >>Cc: Menon, Nishanth; Kevin Hilman; Gopinath, Thara; Peter p2 De Schrijver
> >>Subject: [PATCH 2/2] omap3: sr: improve errors handling
> >>
> >>From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> >>
> >>Do not forget to check the 'platform_device_add_data()' error code
> >>in 'omap_device_build_ss()'.
>
> Hello Artem,
>
> Can we have a better subject and description. The subject esp has got
> nothing to do with the fix.
Hmm, I do not see why you think so. I think the subject is fine - the
patch improves error handling in the SR code. Then description says how
exactly it improves it - it makes the code to not forget to check the
return code, and it tells in which function and which return code.
So the logic is:
1. The subject line is a short description which gives the idea what the
commit is about. So, my subject line says:
1.1. It is about omap3 (which is true)
1.2. It is about sr (which is true)
1.3. It improves error handling (which is also true)
So the subject line is descriptive enough. It does not have to provide
all glory details.
Then the description provides the details.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-09 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 13:20 [PATCH 1/2] omap3: sr: fix memory leak and simplify the code Artem Bityutskiy
2010-07-09 13:20 ` [PATCH 2/2] omap3: sr: improve errors handling Artem Bityutskiy
2010-07-09 15:02 ` Nishanth Menon
2010-07-09 15:05 ` Gopinath, Thara
2010-07-09 15:44 ` Artem Bityutskiy [this message]
2010-07-09 15:51 ` Nishanth Menon
2010-07-09 15:50 ` Artem Bityutskiy
2010-07-09 16:00 ` Menon, Nishanth
2010-07-09 16:02 ` Artem Bityutskiy
2010-07-12 13:36 ` Artem Bityutskiy
2010-07-09 13:22 ` [PATCH 1/2] omap3: sr: fix memory leak and simplify the code Artem Bityutskiy
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=1278690245.9953.142.camel@localhost \
--to=dedekind1@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.de-schrijver@nokia.com \
--cc=thara@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox