All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: Mason <slash.tmp@free.fr>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs
Date: Fri, 9 Oct 2015 15:46:23 +0200	[thread overview]
Message-ID: <5617C52F.9040309@sigmadesigns.com> (raw)
In-Reply-To: <5617C028.3040709@linaro.org>

On 09/10/2015 15:24, Daniel Lezcano wrote:
> On 10/09/2015 02:13 PM, Marc Gonzalez wrote:
>> Sigma Designs Tango platforms provide a 27 MHz crystal oscillator.
>> Use it for clocksource, sched_clock, and delay_timer.
>>
>> Signed-off-by: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
>> ---
>> I have a nagging feeling that the QUIT_IF macro will get this patch NAKed ;-)
>> My rationale: error-handling tends to take the focus away from the normal
>> path, and put it on the error path. Hiding the details away in a macro
>> helps to keep the error-handling noise to a minimum.
> 
> It is a right feeling :)
> 
> The Linux kernel code follows the same path all across the different 
> sub-systems. So it is not a problem to write: if (err) ..., people is 
> used to read such code and by introducing this macro, that makes the 
> code less readable for them.
> 
> Moreover, the way you wrote the macro is strongly discouraged in the 
> CodingStyle document because there is a 'return' inside.

New patch coming right up.

On a tangential subject, it would seem that platforms with verbose logs
at init might benefit from marking as __initconst strings used in __init
functions.

I discussed this some time ago:
https://lkml.org/lkml/2015/3/25/688

which pointed to an earlier discussion:
https://lkml.org/lkml/2014/8/21/255
https://lkml.org/lkml/2014/6/22/149

Regards.


  reply	other threads:[~2015-10-09 13:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 15:10 [PATCH v1] clocksource: Sigma Designs Tango 27 MHz xtal Marc Gonzalez
2015-10-06 23:09 ` Daniel Lezcano
2015-10-07  8:23   ` Marc Gonzalez
2015-10-07  9:47     ` Daniel Lezcano
2015-10-07 11:14       ` Marc Gonzalez
2015-10-07 11:35         ` Daniel Lezcano
2015-10-07 11:35     ` [PATCH v2] clocksource/drivers/tango_xtal: Add new timer for Tango SoCs Marc Gonzalez
2015-10-07 12:31       ` Daniel Lezcano
2015-10-07 13:17         ` Marc Gonzalez
2015-10-07 16:03           ` Daniel Lezcano
2015-10-07 20:12             ` Mason
2015-10-09 12:13               ` [PATCH v3] " Marc Gonzalez
2015-10-09 13:24                 ` Daniel Lezcano
2015-10-09 13:46                   ` Marc Gonzalez [this message]
2015-10-09 14:21                     ` Daniel Lezcano
2015-10-09 16:39                       ` Nicolas Pitre
2015-10-09 14:37                   ` [PATCH v4] " Marc Gonzalez
2015-10-09 14:42                     ` Daniel Lezcano
2015-10-09 14:59                       ` [PATCH v5] " Marc Gonzalez
2015-10-16 12:07                         ` Daniel Lezcano
2015-10-09 14:51                     ` [PATCH v4] " Måns Rullgård
2015-10-09 15:42                       ` Marc Gonzalez
2015-10-09 16:01                         ` Måns Rullgård
2015-10-09 16:36                           ` Marc Gonzalez

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=5617C52F.9040309@sigmadesigns.com \
    --to=marc_gonzalez@sigmadesigns.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slash.tmp@free.fr \
    --cc=tglx@linutronix.de \
    /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.