From: paul.gortmaker@windriver.com (Paul Gortmaker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -next] ARM: pxa: remove duplicated include from spitz.c
Date: Tue, 23 Aug 2016 14:32:50 -0400 [thread overview]
Message-ID: <20160823183249.GE6006@windriver.com> (raw)
In-Reply-To: <87poozpfl0.fsf@belgarion.home>
[Re: [PATCH -next] ARM: pxa: remove duplicated include from spitz.c] On 23/08/2016 (Tue 19:20) Robert Jarzmik wrote:
> Wei Yongjun <weiyj.lk@gmail.com> writes:
>
> > Hi Robert,
> > On 08/24/2016 12:24 AM, Robert Jarzmik wrote:
> >> Wei Yongjun <weiyj.lk@gmail.com> writes:
> >>
> >>> Remove duplicated include.
> >> How so duplicated ? Can you elaborate please ?
> >>
> >> Moreover, how do you do think symbol_get() can stay in spitz.c without having
> >> this include ?
> >
> > file linux/module.h included twice as following:
> >
> > #include <linux/kernel.h>
> > #include <linux/module.h> /* symbol_get ; symbol_put */
> > ...
> > #include <linux/module.h>
> >
> > So I think we can remove the dup include.
>
> Ah I see it now.
>
> What you really mean is that you want to revert 12beb346710b ("Merge tag
> 'pxa-fixes-v4.8' of https://github.com/rjarzmik/linux into randconfig-4.8"),
> because :
> - I wasn't carefull enough at review time of
> https://github.com/rjarzmik/linux/commit/5351ca4e70f30e0175265fbf98691528b9a4e990
> https://github.com/rjarzmik/linux/commit/a3c747b96df66a7eb810fef45f3b9e65614712d9
>
> - and because Paul wasn't very carefull when we look at :
> 73017a542fd2 ("arm: fix implicit module.h users by adding it to arch/arm as
> required.")
>
> So all in all, I'd prefer a revert with Paul's ack please.
So if possible, please drop the duplicate module.h w/o the comment
vs. a revert. Since it appeared as a pseudo merge and was not my
original commit anyway, this shouldn't be a problem I hope...
You can call it careless if you want, I won't be offended -- FWIW I was
juggling several different streams; one to audit and remove apparently
non-required inclusions of module.h and one to unwind the implicit gpio
inclusion presence before trying to pave the way to fixing _that_ last
minute for 4.8; it was mixing and testing the two simulatenously that
led to the removal and re-addition; which when separating out the latter
caused it to become a duplicate additon as reported above.
Not an excuse; just one of those happenstance corner cases. I'd since
fixed the dup locally and added this to my automated testing:
make includecheck |sort > /tmp/pre-include.txt
<...apply all WIP patches>
make includecheck |sort > /tmp/post-include.txt
diff -u /tmp/pre-include.txt /tmp/post-include.txt > /tmp/inc-delta.txt
if [ -s /tmp/inc-delta.txt ]; then
echo redundant includes changed.
cat /tmp/inc-delta.txt
fi
> And this time I'll go through my pxa/for-next tree, I was a fool to
> put that in pxa/fixes.
Well, you were not a fool - the fault is mine if it belongs to anyone.
You made a sensible call based on what I wrote in the commit log.
Fortunately it is 100% harmless and if you want to clean it up locally
and do so ASAP, then no problem -- do it and consider it Ack'd.
Thanks,
Paul.
--
>
> Cheers.
>
> -- Robert
prev parent reply other threads:[~2016-08-23 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:18 [PATCH -next] ARM: pxa: remove duplicated include from spitz.c Wei Yongjun
2016-08-23 16:24 ` Robert Jarzmik
2016-08-23 16:43 ` Wei Yongjun
2016-08-23 17:20 ` Robert Jarzmik
2016-08-23 18:32 ` Paul Gortmaker [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=20160823183249.GE6006@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).