From: Valdis.Kletnieks@vt.edu
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, linux-doc@vger.kernel.org,
Sonal Santan <sonal.santan@gmail.com>
Subject: Re: [PATCH 1/2] platform: x86: dell-smo8800: Dell Latitude freefall driver (ACPI SMO8800/SMO8810)
Date: Tue, 20 May 2014 14:36:18 -0400 [thread overview]
Message-ID: <22163.1400610978@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 20 May 2014 20:10:28 +0200." <201405202010.28868@pali>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Tue, 20 May 2014 20:10:28 +0200, Pali Rohár said:
> > Hmm.. what tree are you building against? I wonder if your
> > checkpatch is a different version than mine (next-20140519).
>
> I'm using up-to-date linus tree, git rev
> 60b5f90d0fac7585f1a43ccdad06787b97eda0ab
Ah, OK. Linux-next tree has a bunch of changes to checkpatch.pl that
will probably go into the Linus tree during the next merge window, and
several of them address the "blank line after declarations" warning - they
roughly tripled the number of checks made for that case....
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-05-20 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 10:47 [PATCH 0/2] " Pali Rohár
2014-05-03 10:47 ` [PATCH 1/2] platform: x86: dell-smo8800: " Pali Rohár
2014-05-07 16:29 ` One Thousand Gnomes
2014-05-20 7:00 ` Valdis.Kletnieks
2014-05-20 8:56 ` Pali Rohár
2014-05-20 18:02 ` Valdis.Kletnieks
2014-05-20 18:10 ` Pali Rohár
2014-05-20 18:36 ` Valdis.Kletnieks [this message]
2014-05-22 11:15 ` [PATCH v2] " Pali Rohár
2014-05-28 13:31 ` Pali Rohár
2014-06-06 10:24 ` Pali Rohár
2014-05-03 10:47 ` [PATCH 2/2] Documentation: Rename hpfall.c => freefall.c, fixes for Dell Pali Rohár
2014-06-11 8:02 ` [PATCH v2] " Pali Rohár
2014-06-14 8:53 ` Pavel Machek
2014-06-16 11:55 ` Pali Rohár
2014-06-27 19:08 ` Pali Rohár
2014-06-27 20:25 ` Randy Dunlap
2014-06-29 2:12 ` Randy Dunlap
2014-07-07 18:15 ` Pali Rohár
2014-07-08 22:49 ` Randy Dunlap
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=22163.1400610978@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sonal.santan@gmail.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
all inboxes | Powered by JetHome®