From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, sfr@canb.auug.org.au
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org, rusty@rustcorp.com.au
Subject: Re: [PATCH v2] VERIFY_OCTAL_PERMISSIONS: Move to <linux/sysfs.h> where it belongs
Date: 15 Dec 2014 19:14:53 -0500 [thread overview]
Message-ID: <20141216001453.1808.qmail@ns.horizon.com> (raw)
In-Reply-To: <20141216100957.6f42e898@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Please do *not* mix changes up like this. Split this out into a
> separate patch, please (1 logical change per patch).
Um... I thought I was doing that. More particularly, the task of
untangling header file dependencies eseemed sufficiently cohesive
that it could be considered one logical change.
It was one round of thinking and analysis about what declarations the
affected files depend on.
Although syntactically possible, given the small size of the change (I
deleted a total of 5 #includes, 2 from moduleparam.h and 3 from sysfs.h),
it didn't seem worth breaking it up further.
> And testing only
> on x86_64 is not "sure" when talking about header file pruning (but at
> least you did the "all" configs).
Well, the first round was reading and understanding the headers; the
compile was just to make sure.
The files I was messing with (moduleparam.h and sysfs.h) don't have a
lot of architecture-specificness within them. The main danger is that
they're used in a zillion places and some caller might depend on the
over-inclusion.
I was rushing to get that to Andrew while the coversation was ongoing
(if you check the mail headers, only a few minutes separated the various
messages) so I was less cautious than usual, but given that a mistake
would result in a nice obvious compile error (with an almost as obvious
fix), it seemed worth the risk.
If my haste made me judge wrong, I apologize. Was I very wrong, or just
a bit over the line?
next prev parent reply other threads:[~2014-12-16 0:14 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
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 [this message]
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=20141216001453.1808.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 \
--cc=sfr@canb.auug.org.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