Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: andriy.shevchenko@linux.intel.com <andriy.shevchenko@linux.intel.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 00/62] Add definition for GPIO direction
Date: Tue, 5 Nov 2019 16:28:36 +0200	[thread overview]
Message-ID: <20191105142836.GS32742@smile.fi.intel.com> (raw)
In-Reply-To: <20191105134026.vl6h6kghuzmslptx@pengutronix.de>

On Tue, Nov 05, 2019 at 02:40:26PM +0100, Uwe Kleine-K?nig wrote:
> On Tue, Nov 05, 2019 at 03:30:25PM +0200, andriy.shevchenko at linux.intel.com wrote:
> > On Tue, Nov 05, 2019 at 02:10:38PM +0100, Uwe Kleine-K?nig wrote:
> > > On Tue, Nov 05, 2019 at 12:54:55PM +0000, Vaittinen, Matti wrote:
> > > > On Tue, 2019-11-05 at 14:20 +0200, Andy Shevchenko wrote:
> > > > > I would also like to see bloat-o-meter statistics before and after
> > > > > your patch.
> > > > > My guts tell me that the result will be not in the favour of yours
> > > > > solution.
> > > > 
> > > > Can you please tell me what type of stats you hope to see? I can try
> > > > generating what you are after. The cover letter contained typical +/-
> > > > change stats from git and summary:
> > > > 
> > > > 62 files changed, 228 insertions(+), 104 deletions(-)
> > > 
> > > I guess he wants to see
> > > 
> > > 	scripts/bloat-o-meter vmlinuz.old vmlinuz
> > 
> > Yes, but be sure you have compiled them all and build them all in.
> > Otherwise you might get wrong result.
> > 
> > > . I would expect a 0 there. I didn't look in detail, but in general I
> > > like the idea to give 0 and 1 a symbolic name.
> > 
> > I'll will be fine with that if and only if maintainers are okay. For now,
> > I don't like the idea to trade bad for worse.
> 
> I don't see you concern.
> 
> 	int somefunction(...)
> 	{
> 		return 1;
> 	}
> 
> is definitively worse than
> 
> 	int somefunction(...)
> 	{
> 		return GPIO_LINE_DIRECTION_IN;
> 	}
> 
> and after cpp had its go on the source the compiler sees the exact same
> thing, so I don't expect any size changes. The only change is that to
> write (or understand) the above code, you have to know that 1
> corresponds to GPIO input (or was it output?) while in the later
> function it is obvious that we're talking about an input.

In almost all cases I'm involved in the original code is different:

	return !!foo();

vs.

	if (foo())
		return A;
	return B;

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2019-11-05 14:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 10:09 [PATCH 00/62] Add definition for GPIO direction Matti Vaittinen
2019-11-05 10:42 ` [PATCH 62/62] gpiolib: Nag for INPUT direction values other than GPIO_LINE_DIRECTION_IN Matti Vaittinen
2019-11-05 10:54 ` [PATCH 00/62] Add definition for GPIO direction Vaittinen, Matti
2019-11-05 12:20 ` Andy Shevchenko
2019-11-05 12:54   ` Vaittinen, Matti
2019-11-05 13:10     ` Uwe Kleine-König
2019-11-05 13:30       ` Vaittinen, Matti
2019-11-05 13:36         ` Uwe Kleine-König
2019-11-05 14:00           ` Vaittinen, Matti
2019-11-05 14:59             ` Uwe Kleine-König
2019-11-05 15:06               ` Vaittinen, Matti
2019-11-05 15:17               ` andriy.shevchenko
2019-11-05 13:30       ` andriy.shevchenko
2019-11-05 13:40         ` Uwe Kleine-König
2019-11-05 14:28           ` andriy.shevchenko [this message]
2019-11-05 13:11     ` andriy.shevchenko
2019-11-05 13:54       ` Vaittinen, Matti
2019-11-05 14:32         ` andriy.shevchenko
2019-11-05 13:10 ` [RESEND PATCH 01/62] gpio: " Matti Vaittinen

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=20191105142836.GS32742@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-aspeed@lists.ozlabs.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