From: Jason Cooper <jason@lakedaemon.net>
To: Eric Rost <eric.rost@mybabylon.net>
Cc: Greg KH <gregkh@linuxfoundation.org>,
jake@lwn.net, antonysaraev@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: skein: Fixed Conditional white space problems
Date: Mon, 29 Sep 2014 21:00:11 -0400 [thread overview]
Message-ID: <20140930010011.GL23926@titan.lakedaemon.net> (raw)
In-Reply-To: <1412037611.10874.1.camel@debian-compaq>
Eric,
On Mon, Sep 29, 2014 at 07:40:11PM -0500, Eric Rost wrote:
> > >I'll be looking to see that no object
> > code has changed (./scripts/objdiff) across your patch series.
>
> Hmm... I'm thinking of digging into it, but I'm not sure the #if's can
> be gotten rid of sans object code changes, since its picking codeblocks
> in the precompiler stage, right?
You just have to remain consistent with what's currently being selected.
But yes, you are correct.
And don't get yourself too tied up in knots wrt objdiff-perfection. I
would take a look at what Joe Perches posted as a starting point. I
haven't reviewed it in depth yet as I'm wrapped around the axle with
other commitments.
If you get stuck, just ask. A *little* beating your head against the
wall is part of the learning process, a lot is just unnecessary
frustration.
wrt to this code, we don't necessarily need to see the macros and such
removed. First step, get them out of the middle of functions. Second
step, decide which would be better off as static inline functions. The
rest may be able to go into a common include.
thx,
Jason.
prev parent reply other threads:[~2014-09-30 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 22:08 Eric Rost
2014-09-28 22:14 ` Greg KH
2014-09-28 23:02 ` Jason Cooper
2014-09-30 0:40 ` Eric Rost
2014-09-30 1:00 ` Jason Cooper [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=20140930010011.GL23926@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=antonysaraev@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric.rost@mybabylon.net \
--cc=gregkh@linuxfoundation.org \
--cc=jake@lwn.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®