From: Pavel Machek <pavel@ucw.cz>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: ncase@xes-inc.com, linux-leds@vger.kernel.org
Subject: Re: [bug report] leds: Add support for Philips PCA955x I2C LED drivers
Date: Thu, 17 Aug 2017 15:58:10 +0200 [thread overview]
Message-ID: <20170817135810.GA21007@amd> (raw)
In-Reply-To: <20170817134937.cdtjl2da33drlmr4@mwanda>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Thu 2017-08-17 16:49:37, Dan Carpenter wrote:
> Never mind, Pavel didn't write this code. Sorry, Nate. This code is
> nice enough. Pavel is just making me annoyed with his constant waste of
> time responses to what are essentially automated emails.
It is you that is wasting people's time with automated emails and
lying subjects... then claiming that people can fix that in their
procmailrc.
If your favourite toy maybe flagged something in the code, mark it as
such. That toy has rather lot of false-positives. Its sibling toy
broke boot for me not-too recently.
If you have to do "essentially automated" emails, at least take care
to make it clear in the subject.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-17 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 10:28 [bug report] leds: Add support for Philips PCA955x I2C LED drivers Dan Carpenter
2017-08-17 11:27 ` Pavel Machek
2017-08-17 11:51 ` Dan Carpenter
2017-08-17 13:27 ` Pavel Machek
2017-08-17 13:37 ` Dan Carpenter
2017-08-17 13:43 ` Dan Carpenter
2017-08-17 13:49 ` Dan Carpenter
2017-08-17 13:58 ` Pavel Machek [this message]
2017-08-17 13:58 ` Nate Case
2017-08-17 14:01 ` Dan Carpenter
2017-08-17 11:28 ` Pavel Machek
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=20170817135810.GA21007@amd \
--to=pavel@ucw.cz \
--cc=dan.carpenter@oracle.com \
--cc=linux-leds@vger.kernel.org \
--cc=ncase@xes-inc.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