From: Randy Dunlap <rdunlap@infradead.org>
To: Peter Foley <pefoley2@pefoley.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files
Date: Tue, 02 Sep 2014 16:24:35 -0700 [thread overview]
Message-ID: <540651B3.8030400@infradead.org> (raw)
In-Reply-To: <CAOFdcFP4b0YFMuUFKm4=FoAGbCObf4u=W0UUPwf-ju_TNvuJaA@mail.gmail.com>
On 09/02/14 15:58, Peter Foley wrote:
> On Mon, Aug 25, 2014 at 4:33 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 04/17/14 07:11, Peter Foley wrote:
>> Hi Peter,
>>
>> Sorry about the delay and thanks for the patches.
>>
>> I have now applied all 4 of these patches, with a few small changes in
>> Documentation/laptops/ to account for hpfall.c being renamed to freefall.c
>> and the problems with it having already been fixed by other patches.
>>
>> [testing]
>>
>> Documentation/vDSO/* does not build for me:
>>
>> HOSTCC Documentation/vDSO/parse_vdso.o
>> HOSTCC Documentation/vDSO/vdso_test.o
>> LD Documentation/video4linux/built-in.o
>> HOSTLD Documentation/vDSO/vdso_test
>> CC [M] Documentation/video4linux/v4l2-pci-skeleton.o
>> /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: warning: cannot find entry symbol _start; defaulting to 000000000040017c
>> Documentation/vDSO/parse_vdso.o: In function `vdso_match_version':
>> parse_vdso.c:(.text+0x48e): undefined reference to `strcmp'
>> Documentation/vDSO/parse_vdso.o: In function `vdso_sym':
>> parse_vdso.c:(.text+0x59c): undefined reference to `strcmp'
>> Documentation/vDSO/vdso_test.o: In function `main':
>> vdso_test.c:(.text+0x15): undefined reference to `getauxval'
>> vdso_test.c:(.text+0x2a): undefined reference to `puts'
>> vdso_test.c:(.text+0x3e): undefined reference to `getauxval'
>> vdso_test.c:(.text+0x6a): undefined reference to `puts'
>> vdso_test.c:(.text+0xa8): undefined reference to `printf'
>> vdso_test.c:(.text+0xb4): undefined reference to `puts'
>> collect2: error: ld returned 1 exit status
>> make[3]: *** [Documentation/vDSO/vdso_test] Error 1
>>
>> I have all of the others building and vDSO commented out for now.
>>
>> Any suggestions, ideas, or fixes?
>>
>>
>> Also, I haven't checked each source file individually, but I expect that
>> many of these are tools that could (should) be moved to $srctree/tools,
>> if you or anyone else is interested in that.
>>
>> Thanks,
>> --
>> ~Randy
>
> So I finally found the time to look at the vDSO test and figure out
> what the issue was.
> However, the commits no longer seem to be in linux-next.
> Is there some other tree I should be looking at?
The regular linux-next maintainer is on vacation (or something).
It appears that the interim maintainer didn't import quilt patches for some reason.
I guess the quilt patches will be back whenever Stephen Rothwell is back.
Mark, do you have any ideas about this?
Importing jdelvare-hwmon based on 3.15-rc7
Unknown BASE
Importing rd-docs based on 3.17-rc1
Unknown BASE
Thanks,
--
~Randy
next prev parent reply other threads:[~2014-09-02 23:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 14:11 [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Peter Foley
2014-04-17 14:11 ` [PATCH 2/4] Documentation: add makefiles for more targets Peter Foley
2014-08-26 16:50 ` Andrey Wagin
2014-04-17 14:11 ` [PATCH 3/4] Documentation: make functions static to avoid prototype warnings Peter Foley
2014-04-17 14:11 ` [PATCH 4/4] Documentation: fix misc. warnings Peter Foley
2014-06-29 2:23 ` [PATCH 1/4] Documentation: use subdir-y to avoid unnecessary built-in.o files Randy Dunlap
2014-07-09 20:52 ` Sam Ravnborg
2014-08-25 20:33 ` Randy Dunlap
2014-09-02 22:58 ` Peter Foley
2014-09-02 23:24 ` Randy Dunlap [this message]
2014-09-02 23:29 ` Mark Brown
2014-09-03 23:08 ` Peter Foley
2014-09-03 23:21 ` Mark Brown
2014-09-03 23:38 ` Randy Dunlap
2014-09-03 23:49 ` Mark Brown
2014-09-04 10:42 ` Mark Brown
2014-09-06 0:07 ` Randy Dunlap
2014-09-07 17:59 ` Randy Dunlap
2014-09-07 18:48 ` Mark Brown
2014-09-07 20:52 ` Randy Dunlap
2014-09-08 8:03 ` Stephen Rothwell
2014-09-08 10:22 ` Mark Brown
2014-09-08 14:57 ` 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=540651B3.8030400@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--cc=sam@ravnborg.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