From: Sri <sjayaram@akamai.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Eric B Munson <emunson@akamai.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [PATCH V2] Test compaction of mlocked memory
Date: Wed, 06 May 2015 13:44:44 -0400 [thread overview]
Message-ID: <554A530C.4050109@akamai.com> (raw)
In-Reply-To: <554A525A.8000401@osg.samsung.com>
Thanks!
-Sri
On 05/06/2015 01:41 PM, Shuah Khan wrote:
> On 05/06/2015 11:28 AM, Sri wrote:
>> Hi Shuah,
>>
>> This is what I see when I check the patch against the script,
>>
>> linux-stable$ ./scripts/checkpatch.pl
>> 0001-Test-compaction-of-mlocked-memory.patch
>> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
>> #72:
>> new file mode 100644
>>
>> total: 0 errors, 1 warnings, 256 lines checked
>>
>> 0001-Test-compaction-of-mlocked-memory.patch has style problems, please
>> review.
>>
>> If any of these errors are false positives, please report
>> them to the maintainer, see CHECKPATCH in MAINTAINERS.
>>
>>
>> That was the only warning I saw even before I submitted the patch. I'm
>> not sure how the whitespaces are introduced...
>>
>
> Hmm. Perhaps something is odd with the 4.1 checkpatch script.
> I am not seeing any whitespace errors when I do a manual
> check on the patch file.
>
> Applying to linux-kselftest next
>
> -- Shuah
>
>
prev parent reply other threads:[~2015-05-06 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 18:21 [PATCH V2] Test compaction of mlocked memory Sri Jayaramappa
2015-04-23 18:41 ` Eric B Munson
2015-04-23 20:23 ` Andrew Morton
2015-04-23 20:24 ` Shuah Khan
2015-05-06 17:01 ` Shuah Khan
2015-05-06 17:28 ` Sri
2015-05-06 17:41 ` Shuah Khan
2015-05-06 17:44 ` Sri [this message]
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=554A530C.4050109@akamai.com \
--to=sjayaram@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=emunson@akamai.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.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