From: Anuj Mittal <anuj.mittal@intel.com>
To: Jaewon Lee <JAEWON@xilinx.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI
Date: Thu, 2 Aug 2018 09:32:32 +0800 [thread overview]
Message-ID: <c376a5fc-807d-6475-9be7-0203ac703b35@intel.com> (raw)
In-Reply-To: <MWHPR02MB27684D092677AC56F96464DAAF2C0@MWHPR02MB2768.namprd02.prod.outlook.com>
On 08/02/2018 08:27 AM, Jaewon Lee wrote:
> Hi Anuj,
>
> Thanks for the reply
> That is a good point, will send a v2 that also deals with patches.
> Regarding other scc files, according to the kernel dev manual,
> "It is only necessary to specify the .scc files on the SRC_URI."
>
> So from my understanding all scc files will be in SRC_URI which means they get parsed by this fix,
> Is this not the case?
If a scc file, foo.scc, includes any other scc file say bar.scc, then it
isn't mandatory to specify bar.scc as part of SRC_URI I think.
You can give it a try by creating empty sccs and including a malformed
patch in a nested scc to see if you get an error while patching.
Thanks,
Anuj
prev parent reply other threads:[~2018-08-02 1:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 21:21 [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI Jaewon Lee
2018-07-30 21:21 ` [PATCH] kernel-yocto.bbclass: Adds oe-local-files path (devtool) to include directives Jaewon Lee
2018-08-01 11:25 ` [PATCH] devtool-source.bbclass: Support kernel fragments not in SRC_URI Anuj Mittal
2018-08-01 23:30 ` Alejandro Enedino Hernandez Samaniego
2018-08-02 2:55 ` Anuj Mittal
2018-08-02 8:53 ` Richard Purdie
2018-08-02 20:55 ` Alejandro Enedino Hernandez Samaniego
2018-08-10 2:36 ` Anuj Mittal
[not found] ` <MWHPR02MB27684D092677AC56F96464DAAF2C0@MWHPR02MB2768.namprd02.prod.outlook.com>
2018-08-02 1:32 ` Anuj Mittal [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=c376a5fc-807d-6475-9be7-0203ac703b35@intel.com \
--to=anuj.mittal@intel.com \
--cc=JAEWON@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox