linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: mx5/mx53_evk: Remove unneeded gpio_set_value call
Date: Sun, 20 Mar 2011 22:30:45 +0100	[thread overview]
Message-ID: <20110320213045.GA27943@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1103202143070.27008@ask.diku.dk>

On Sun, Mar 20, 2011 at 09:51:32PM +0100, Julia Lawall wrote:
> I guess that the !GPIOLIB issue is related to a configuration option, that 
> can't very easily be detected from looking at the C file alone?

Yes, that is a configuration option at the moment. It shouldn't be IMO, that's
what my patch is addressing.

> Ignoring that issue, the following semantic patch addresses the common 

Sigh, here goes my chance to play with coccinelle again ;)

> case where there is no error checking for the input or output call, but 
> there may be error checking for the gpio_request call.  This transforms 
> over 500 occurrences.

In my book, converting the ones which do not check errors at all is not worth
the trouble. Proper error-checking should be the main benefit, not one saved
line. So, this is mindwork. If gpio_request is checked, merging seems sensible
(but should be audited).

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110320/a9fbf2da/attachment.sig>

  reply	other threads:[~2011-03-20 21:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 18:21 [PATCH 1/2] ARM: mx5/babbage: Remove unneeded gpio_set_value call Fabio Estevam
2011-03-14 18:21 ` [PATCH 2/2] ARM: mx5/mx53_evk: " Fabio Estevam
2011-03-15  9:06   ` Uwe Kleine-König
2011-03-15  9:41     ` Julia Lawall
2011-03-15  9:49       ` Uwe Kleine-König
2011-03-15 10:19         ` Julia Lawall
2011-03-15 10:29           ` Wolfram Sang
2011-03-16  8:33           ` Uwe Kleine-König
2011-03-16  9:15             ` Julia Lawall
2011-03-16 14:19             ` Fabio Estevam
2011-03-20 17:56             ` Julia Lawall
2011-03-20 19:24               ` Wolfram Sang
2011-03-20 20:51                 ` Julia Lawall
2011-03-20 21:30                   ` Wolfram Sang [this message]
2011-03-20 21:42                     ` Julia Lawall
2011-03-20 21:04                 ` Julia Lawall
2011-03-21  7:43                   ` Grant Likely
2011-03-21  7:59                     ` Julia Lawall
2011-03-21  7:48           ` Grant Likely
2011-03-21  8:01             ` Julia Lawall

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=20110320213045.GA27943@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).