[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <547F33AC.50002@users.sourceforge.net>
Date: Wed, 03 Dec 2014 17:00:44 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Arend van Spriel <arend@...adcom.com>
CC: Dan Carpenter <dan.carpenter@...cle.com>,
Julia Lawall <julia.lawall@...6.fr>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Coccinelle <cocci@...teme.lip6.fr>, backports@...r.kernel.org,
Johannes Berg <johannes@...solutions.net>,
"Luis R. Rodriguez" <mcgrof@...e.com>
Subject: Re: [patch] CodingStyle: add some more error handling guidelines
>> Which name pattern do you find more appropriate in such
>> an use case?
>
> I think Dan wants the label to be descriptive about the tasks
> needed in the exception handling itself.
I would usually prefer also such a target-oriented labelling
for the affected identifiers.
How are the chances to express an expectation in this direction
unambiguously for the proposed coding style update?
> This makes sense as the exception handling steps may be reused
> for different failures in the code.
I would stress a different reason from my point of view.
Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists