From: Joe Perches <joe@perches.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
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:03:11 -0700 [thread overview]
Message-ID: <1457985791.11972.128.camel@perches.com> (raw)
In-Reply-To: <56E71825.5070104@osg.samsung.com>
On Mon, 2016-03-14 at 16:59 -0300, Javier Martinez Canillas wrote:
> I don't think they make little sense now since even a non-native english
> speaker like me can understand it :)
That's a non sequitur if ever I read one.
> But yes, it's cryptic at the very least. That's the problem with long tex=
t
> and the 80 char limit to make checkpatch.pl happy. I guess I can just mov=
e
> the message a little bit even if that will make to not be properly aligne=
d.
There's no issue with longer than 80 column lines
for these messages. =C2=A0checkpatch wouldn't complain.
--=20
--=20
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.
---=20
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 e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-03-14 20:03 UTC|newest]
Thread overview: 10+ 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:11 ` [rtc-linux] " Joe Perches
2016-03-14 19:31 ` Javier Martinez Canillas
2016-03-14 19:38 ` Joe Perches
2016-03-14 19:59 ` Javier Martinez Canillas
2016-03-14 20:03 ` Joe Perches [this message]
2016-03-14 20:23 ` Javier Martinez Canillas
2016-03-14 20:19 ` Alexandre Belloni
2016-03-14 20:33 ` Joe Perches
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=1457985791.11972.128.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox