From: Joe Perches <joe@perches.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH] rtc: s3c: Don't print an error on probe deferral
Date: Mon, 14 Mar 2016 13:33:08 -0700 [thread overview]
Message-ID: <1457987588.11972.135.camel@perches.com> (raw)
In-Reply-To: <20160314201958.GB28277@piout.net>
On Mon, 2016-03-14 at 21:19 +0100, Alexandre Belloni wrote:
> checkpatch will not complain for messages but it will definitively
> complain if they are not properly aligned:)
checkpatch wouldn't actually complain unless the --strict option
was used or these files were in drivers/net or drivers/staging.
--
--
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: Joe Perches <joe@perches.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
rtc-linux@googlegroups.com
Subject: Re: [PATCH] rtc: s3c: Don't print an error on probe deferral
Date: Mon, 14 Mar 2016 13:33:08 -0700 [thread overview]
Message-ID: <1457987588.11972.135.camel@perches.com> (raw)
In-Reply-To: <20160314201958.GB28277@piout.net>
On Mon, 2016-03-14 at 21:19 +0100, Alexandre Belloni wrote:
> checkpatch will not complain for messages but it will definitively
> complain if they are not properly aligned:)
checkpatch wouldn't actually complain unless the --strict option
was used or these files were in drivers/net or drivers/staging.
next prev parent reply other threads:[~2016-03-14 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 19:05 [rtc-linux] [PATCH] rtc: s3c: Don't print an error on probe deferral Javier Martinez Canillas
2016-03-14 19:05 ` Javier Martinez Canillas
2016-03-14 19:11 ` [rtc-linux] " Joe Perches
2016-03-14 19:11 ` Joe Perches
2016-03-14 19:31 ` [rtc-linux] " Javier Martinez Canillas
2016-03-14 19:31 ` Javier Martinez Canillas
2016-03-14 19:38 ` [rtc-linux] " Joe Perches
2016-03-14 19:38 ` Joe Perches
2016-03-14 19:59 ` [rtc-linux] " Javier Martinez Canillas
2016-03-14 19:59 ` Javier Martinez Canillas
2016-03-14 20:03 ` [rtc-linux] " Joe Perches
2016-03-14 20:03 ` Joe Perches
2016-03-14 20:23 ` [rtc-linux] " Javier Martinez Canillas
2016-03-14 20:23 ` Javier Martinez Canillas
2016-03-14 20:19 ` [rtc-linux] " Alexandre Belloni
2016-03-14 20:19 ` Alexandre Belloni
2016-03-14 20:33 ` Joe Perches [this message]
2016-03-14 20:33 ` Joe Perches
2016-03-14 20:51 ` [rtc-linux] " Alexandre Belloni
2016-03-14 20:51 ` 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=1457987588.11972.135.camel@perches.com \
--to=joe@perches.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--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.