From: Mark Hounschell <markh@compro.net>
To: Greg KH <gregkh@linuxfoundation.org>, Joe Perches <joe@perches.com>
Cc: devel <devel@driverdev.osuosl.org>,
Lidza Louina <lidza.louina@gmail.com>,
DaeSeok Youn <daeseok.youn@gmail.com>,
driverdev-devel@linuxdriverproject.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] staging: dgap: re-arrange functions for removing forward declarations.
Date: Tue, 14 Oct 2014 08:01:27 -0400 [thread overview]
Message-ID: <543D1097.7010709@compro.net> (raw)
In-Reply-To: <1441864556.1190074.1413252337243.JavaMail.root@mx2.compro.net>
On 10/13/2014 10:04 PM, Greg KH wrote:
> On Mon, Oct 13, 2014 at 07:56:38AM -0700, Joe Perches wrote:
>> On Mon, 2014-10-13 at 17:01 +0900, DaeSeok Youn wrote:
>>> Hi,
>>>
>>> 2014-10-13 12:25 GMT+09:00 Greg KH <gregkh@linuxfoundation.org>:
>>>> On Mon, Oct 13, 2014 at 11:34:25AM +0900, Daeseok Youn wrote:
>>>>> Re-arrange the functions for removing forward declarations.
>>>>>
>>>>> Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
>>>>> ---
>>>>> This patch has too many changes for re-arranging the functions.
>>>>> So I wonder that I should break this up into smaller patches.
>>>>
>>>> Are the .o files identical before and after this patch? If so, it's
>>>> fine.
>>> Ok. I will check for that.
>>
>> The .o files shouldn't be identical after function reordering.
>
> Hm, they might be the same size, but I can see how on some
> architectures (like ppc) how that would not be the case, you are right.
>
> Isn't there an "objdiff" program or something like that which might help
> in validating that nothing "changed" in the source for type of patch
> that just moves functions around in a file.
>
> thanks,
>
Greg,
Would just testing the thing be of any help?
Regards
Mark
next prev parent reply other threads:[~2014-10-14 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 2:34 [PATCH] staging: dgap: re-arrange functions for removing forward declarations Daeseok Youn
2014-10-13 3:25 ` Greg KH
2014-10-13 8:01 ` DaeSeok Youn
2014-10-13 14:56 ` Joe Perches
2014-10-13 23:44 ` DaeSeok Youn
2014-10-14 2:04 ` Greg KH
2014-10-14 2:19 ` Joe Perches
2014-10-14 11:10 ` DaeSeok Youn
2014-10-14 13:04 ` Dan Carpenter
[not found] ` <1441864556.1190074.1413252337243.JavaMail.root@mx2.compro.net>
2014-10-14 12:01 ` Mark Hounschell [this message]
[not found] ` <1480715134.1194532.1413288717130.JavaMail.root@mx2.compro.net>
2014-10-21 18:00 ` Mark Hounschell
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=543D1097.7010709@compro.net \
--to=markh@compro.net \
--cc=daeseok.youn@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=lidza.louina@gmail.com \
--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