From: Nishanth Menon <nm@ti.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "Gopinath, Thara" <thara@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
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, 9 Jul 2010 10:51:33 -0500 [thread overview]
Message-ID: <4C374585.7030104@ti.com> (raw)
In-Reply-To: <1278690245.9953.142.camel@localhost>
Artem Bityutskiy had written, on 07/09/2010 10:44 AM, the following:
> 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)
I think Thara's contention is that this is omap_device related- yeah SR
is one of the users of omap_device, but there are much more folks using
omap_device in l-o today.
> 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.
>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-07-09 15:51 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
2010-07-09 15:51 ` Nishanth Menon [this message]
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=4C374585.7030104@ti.com \
--to=nm@ti.com \
--cc=dedekind1@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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 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.