From: "George Spelvin" <linux@horizon.com>
To: akpm@linux-foundation.org, linux@horizon.com
Cc: linux-kernel@vger.kernel.org, rdunlap@infradead.org,
rusty@rustcorp.com.au
Subject: Re: [PATCH] [PATCH] VERIFY_OCTAL_PERMISSIONS: Move to <linux/sysfs.h> where it belongs
Date: 5 Dec 2014 21:49:52 -0500 [thread overview]
Message-ID: <20141206024952.24901.qmail@ns.horizon.com> (raw)
In-Reply-To: <20141205172802.4c56cbd6.akpm@linux-foundation.org>
>> -----
> This shouldn't be here because "^---" is considered "end of changelog".
Damn it, I couldn't remember how to add not-for-commit comments to a patch.
I RTFMed and thought that was what "git mailinfo --scissors" wanted.
(Normally, I put it down with the diffstat, but preferred a more
prominent place for this conversation.)
> Let's include bug.h into sysfs.h.
It worked without, but yeah... since I can't figure *how* it works.
>> diff --git a/include/linux/moduleparam.h b/include/linux/moduleparam.h
>> index 1c9effa2..974097df 100644
>> --- a/include/linux/moduleparam.h
>> +++ b/include/linux/moduleparam.h
>> @@ -1,9 +1,9 @@
>> #ifndef _LINUX_MODULE_PARAMS_H
>> #define _LINUX_MODULE_PARAMS_H
>> /* (C) Copyright 2001, 2002 Rusty Russell IBM Corporation */
>> -#include <linux/init.h>
>> #include <linux/stringify.h>
>> -#include <linux/kernel.h>
>> +#include <linux/sysfs.h>
>> +#include <linux/types.h>
> Removing the kernel.h inclusion is good, but risky. Are you sure
> there's nothing in moduleparam.h which uses kernel.h things?
Well, I did a quick eyeball-scan, then did my usual build, then
an allyesconfig and an allmodconfig.
I found some other alarming things, but nothing related to this.
E.g.
drivers/net/ethernet/intel/i40e/i40e_debugfs.c: In function 'i40e_dbg_dump_desc':
drivers/net/ethernet/intel/i40e/i40e_debugfs.c:855:1: warning: the frame size of 8192 bytes is larger than 2048 bytes [-Wframe-larger-than=]
}
(Honestly, I didn't wait for the allmodconfig to finish, since I
expected it to fail within the first few hundred modules if it was going to
fail at all, but it has finished now.)
next prev parent reply other threads:[~2014-12-06 2:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 0:07 [PATCH] VERIFY_OCTAL_PERMISSIONS needs <linux/bug.h> George Spelvin
2014-12-06 0:12 ` Randy Dunlap
2014-12-06 0:15 ` Andrew Morton
2014-12-06 1:18 ` [PATCH] [PATCH] VERIFY_OCTAL_PERMISSIONS: Move to <linux/sysfs.h> where it belongs George Spelvin
2014-12-06 1:28 ` Andrew Morton
2014-12-06 2:49 ` George Spelvin [this message]
2014-12-06 2:53 ` Joe Perches
2014-12-06 2:57 ` Jeff Kirsher
2014-12-06 2:58 ` Andrew Morton
2014-12-06 3:23 ` [PATCH v2] " George Spelvin
2014-12-15 3:56 ` Rusty Russell
2014-12-15 23:09 ` Stephen Rothwell
2014-12-16 0:14 ` George Spelvin
2014-12-16 0:31 ` Stephen Rothwell
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=20141206024952.24901.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome