All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	rtc-linux@googlegroups.com
Cc: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	linux-samsung-soc@vger.kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [rtc-linux] Re: [PATCH v3] rtc: s3c: Don't print an error on probe deferral
Date: Fri, 18 Mar 2016 10:56:08 -0300	[thread overview]
Message-ID: <56EC08F8.2080400@osg.samsung.com> (raw)
In-Reply-To: <CAJKOXPeam-rpnijB0OgGxbY2rdtVwqwdEyHb_LOyzZnXuY82vg@mail.gmail.com>

Hello Krzysztof,

On 03/18/2016 09:20 AM, Krzysztof Kozlowski wrote:
> On Fri, Mar 18, 2016 at 9:07 PM, Alexandre Belloni
>> On 18/03/2016 at 08:57:57 -0300, Javier Martinez Canillas wrote :

[snip]

>>>
>>> Just to make sure that I understood correctly, there's no action I
>>> should take in order for this patch to be picked right? IOW, the
>>> current version is OK?
>>>
>>
>> I was kind of waiting an answer on the question whether the core already
>> prints a message when probe dereferral happens because in that case,
>> there is no need for a debug message and we can indeed simplify the
>> whole block.
> 
> Although I did not test it, I think the core will print generic defer
> message. See really_probe() around line 400:
> http://lxr.free-electrons.com/source/drivers/base/dd.c?v=4.4#L347
> 
> However the cause of deferring will not be printed... so I find some
> use of debug message in driver... On the other hand, not many drivers
> are doing this. Ehh, I guess I am just really picky. :)
>

It's Ok, I also have doubts about which direction to take even when
writing trivial patches like $SUBJECT, so I understand the feeling :)

> BR,
> Krzysztof
> 

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	rtc-linux@googlegroups.com
Cc: linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
	linux-samsung-soc@vger.kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [rtc-linux] Re: [PATCH v3] rtc: s3c: Don't print an error on probe deferral
Date: Fri, 18 Mar 2016 10:56:08 -0300	[thread overview]
Message-ID: <56EC08F8.2080400@osg.samsung.com> (raw)
In-Reply-To: <CAJKOXPeam-rpnijB0OgGxbY2rdtVwqwdEyHb_LOyzZnXuY82vg@mail.gmail.com>

Hello Krzysztof,

On 03/18/2016 09:20 AM, Krzysztof Kozlowski wrote:
> On Fri, Mar 18, 2016 at 9:07 PM, Alexandre Belloni
>> On 18/03/2016 at 08:57:57 -0300, Javier Martinez Canillas wrote :

[snip]

>>>
>>> Just to make sure that I understood correctly, there's no action I
>>> should take in order for this patch to be picked right? IOW, the
>>> current version is OK?
>>>
>>
>> I was kind of waiting an answer on the question whether the core already
>> prints a message when probe dereferral happens because in that case,
>> there is no need for a debug message and we can indeed simplify the
>> whole block.
> 
> Although I did not test it, I think the core will print generic defer
> message. See really_probe() around line 400:
> http://lxr.free-electrons.com/source/drivers/base/dd.c?v=4.4#L347
> 
> However the cause of deferring will not be printed... so I find some
> use of debug message in driver... On the other hand, not many drivers
> are doing this. Ehh, I guess I am just really picky. :)
>

It's Ok, I also have doubts about which direction to take even when
writing trivial patches like $SUBJECT, so I understand the feeling :)

> BR,
> Krzysztof
> 

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

  reply	other threads:[~2016-03-18 13:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15  1:38 [rtc-linux] [PATCH v3] rtc: s3c: Don't print an error on probe deferral Javier Martinez Canillas
2016-03-15  1:38 ` Javier Martinez Canillas
2016-03-15  1:50 ` [rtc-linux] " Krzysztof Kozlowski
2016-03-15  1:50   ` Krzysztof Kozlowski
2016-03-15  1:59   ` [rtc-linux] " Javier Martinez Canillas
2016-03-15  1:59     ` Javier Martinez Canillas
2016-03-15  2:26     ` [rtc-linux] " Krzysztof Kozlowski
2016-03-15  2:26       ` Krzysztof Kozlowski
2016-03-15  2:58       ` [rtc-linux] " Javier Martinez Canillas
2016-03-15  2:58         ` Javier Martinez Canillas
2016-03-18 11:57         ` [rtc-linux] " Javier Martinez Canillas
2016-03-18 11:57           ` Javier Martinez Canillas
2016-03-18 12:07           ` [rtc-linux] " Alexandre Belloni
2016-03-18 12:07             ` Alexandre Belloni
2016-03-18 12:20             ` [rtc-linux] " Krzysztof Kozlowski
2016-03-18 12:20               ` Krzysztof Kozlowski
2016-03-18 13:56               ` Javier Martinez Canillas [this message]
2016-03-18 13:56                 ` Javier Martinez Canillas
2016-03-18 13:03             ` Alexandre Belloni
2016-03-18 13:03               ` Alexandre Belloni
2016-03-18 13:44               ` [rtc-linux] " Javier Martinez Canillas
2016-03-18 13:44                 ` Javier Martinez Canillas
2016-03-18 23:08 ` [rtc-linux] " Alexandre Belloni
2016-03-18 23:08   ` Alexandre Belloni

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=56EC08F8.2080400@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=joe@perches.com \
    --cc=k.kozlowski@samsung.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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.