From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Michal Marek <mmarek@suse•cz>
Cc: Randy Dunlap <rdunlap@infradead•org>,
Nicolas Pitre <nicolas.pitre@linaro•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-kbuild <linux-kbuild@vger•kernel.org>
Subject: Re: linux-next: Tree for Apr 22 (adjust_autoksyms.sh)
Date: Tue, 26 Apr 2016 23:07:43 +1000 [thread overview]
Message-ID: <20160426230743.26d00e67@canb.auug.org.au> (raw)
In-Reply-To: <571F4ECC.5020902@suse.cz>
Hi Michal,
On Tue, 26 Apr 2016 13:19:40 +0200 Michal Marek <mmarek@suse•cz> wrote:
>
> On 2016-04-23 00:55, Randy Dunlap wrote:
> > On 04/22/16 12:44, Nicolas Pitre wrote:
> >> On Fri, 22 Apr 2016, Nicolas Pitre wrote:
> >>
> >>> On Fri, 22 Apr 2016, Randy Dunlap wrote:
> >>>
> >>>> Yes, this patch helps, but I think there is still a problem.
> >>>> I think that trim needs to be done after CONFIG_BUILD_DOCSRC and possibly
> >>>> after CONFIG_SAMPLES are built.
> >>>
> >>> The later is already taken care of with commit dd92478a15.
> >>>
> >>>> At least CONFIG_BUILD_DOCSRC seems to
> >>>> cause this error:
> >>>>
> >>>> Setup is 16508 bytes (padded to 16896 bytes).
> >>>> System is 6125 kB
> >>>> CRC 8aa70f94
> >>>> Kernel: arch/x86/boot/bzImage is ready (#9)
> >>>> ERROR: "cn_del_callback" [Documentation/connector/cn_test.ko] undefined!
> >>>> ERROR: "cn_add_callback" [Documentation/connector/cn_test.ko] undefined!
> >>>> ERROR: "cn_netlink_send" [Documentation/connector/cn_test.ko] undefined!
> >>>> ../scripts/Makefile.modpost:91: recipe for target '__modpost' failed
> >>>> make[2]: *** [__modpost] Error 1
> >>>
> >>> This one is indeed a problem.
> >>
> >> Please try the following:
> >
> > Yes, this works. Thanks.
> >
> > Acked-by: Randy Dunlap <rdunlap@infradead•org>
> > Tested-by: Randy Dunlap <rdunlap@infradead•org>
>
> Applied to kbuild.git#kbuild.
Unfortunately, that was the commit I had to revert from linux-next
today - see my email report. It breaks what looks like correct
additions to the block tree.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-04-26 13:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 5:35 linux-next: Tree for Apr 22 Stephen Rothwell
2016-04-22 16:52 ` linux-next: Tree for Apr 22 (adjust_autoksyms.sh) Randy Dunlap
2016-04-22 17:48 ` Nicolas Pitre
2016-04-22 18:22 ` Randy Dunlap
2016-04-22 18:43 ` Nicolas Pitre
2016-04-22 19:44 ` Nicolas Pitre
2016-04-22 22:55 ` Randy Dunlap
2016-04-26 11:19 ` Michal Marek
2016-04-26 13:07 ` Stephen Rothwell [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=20160426230743.26d00e67@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mmarek@suse$(echo .)cz \
--cc=nicolas.pitre@linaro$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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