All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruslan Bilovol <rbilovol@cisco.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
	"Hongzhi, Song" <hongzhi.song@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel-devsrc: copy mmiowb.h and modpost from ${B} of kernel
Date: Fri, 17 Jan 2020 17:49:40 +0200	[thread overview]
Message-ID: <b7d4cf83-c7a9-2d69-7ef5-357f88641372@cisco.com> (raw)
In-Reply-To: <CADkTA4N8y=C--kAD0OD3Lr7+N31XhOhTsE0R_kFiJAoCvUqvVA@mail.gmail.com>

On 9/11/19 2:36 PM, Bruce Ashfield wrote:
> On Wed, Sep 11, 2019 at 5:10 AM Hongzhi, Song
> <hongzhi.song@windriver.com> wrote:
>>
>>
>> On 9/6/19 11:10 AM, Hongzhi, Song wrote:
>>>
>>> On 9/4/19 8:34 PM, Bruce Ashfield wrote:
>>>> On Wed, Sep 4, 2019 at 6:07 AM Hongzhi, Song
>>>> <hongzhi.song@windriver.com> wrote:
>>>>>
>>>>> On 9/4/19 11:55 AM, Bruce Ashfield wrote:
>>>>>> On Tue, Sep 3, 2019 at 9:43 PM Hongzhi.Song
>>>>>> <hongzhi.song@windriver.com> wrote:
>>>>>>> There are two errors when compile an out of tree kernel module
>>>>>>> using sdk:
>>>>>>>
>>>>>> This is not universally true. Can you expand on what kernel version
>>>>>> and architectures you are building ? I'm able to build kernel modules
>>>>>> across all the arches I'm currently testing, so I'd like to capture
>>>>>> your exact config in the long log. Neither is the autobuilder showing
>>>>>> any errors.
>>>>> Hi Bruce,
>>>>>
>>>>>
>>>>> kernel version: 5.0.19

I met the same issue with modpost recently. This is because kernel 5.0
commit 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=60df1aee2aecb53efb4218b4dfdf7d6c80a5a3de
moved modpost out of 'scripts' target.

>> Hi Bruce,
>>
>> I found 2.7 and 2.6 doc all use "make scripts". And now "make scripts"
>> doesn't work.
>>
>> Should the doc be change to "make scripts prepare" ?
> 
> Yes they should be. We need to open a bug and get ScottR to look into it.
> 
> We've (Richard, myself, and others) have been using make scripts
> prepare as a requirement for on kernel building for quite some time
> now. The docs should reflect this.
> 

Looking at kernel sources, there is better alternative for "make scripts
prepare" requirement: "modules_prepare". It's a special Linux Kernel
target to prepare building external modules.
What it does is actually "scripts+prepare" for older kernels (like 3.10)
and "prepare" (which has "scripts" as indirect dependency) in recent
kernels (v5.4 for example)

So instead of custom "make scripts prepare" lets change it in the doc to
official "modules_prepare" target for modules building preparations.

Any objections?

Thanks,
Ruslan



























  reply	other threads:[~2020-01-17 15:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  1:43 [PATCH] kernel-devsrc: copy mmiowb.h and modpost from ${B} of kernel Hongzhi.Song
2019-09-04  3:55 ` Bruce Ashfield
2019-09-04 10:07   ` Hongzhi, Song
2019-09-04 12:34     ` Bruce Ashfield
2019-09-06  3:10       ` Hongzhi, Song
2019-09-11  9:10         ` Hongzhi, Song
2019-09-11 11:36           ` Bruce Ashfield
2020-01-17 15:49             ` Ruslan Bilovol [this message]
2020-01-17 16:40               ` Bruce Ashfield

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=b7d4cf83-c7a9-2d69-7ef5-357f88641372@cisco.com \
    --to=rbilovol@cisco.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=hongzhi.song@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.