From: przemyslaw.hawrylewicz.czarnowski@linux.intel.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] Add nbdkit to extend backend possibilities of nbd.
Date: Fri, 10 Apr 2020 03:17:33 -0700 [thread overview]
Message-ID: <7592.1586513853636817343@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1so7NBe8eLiJmeR0aWcf+A8+624qwRoR_RMHVGSQ94Hz4A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
On Thursday, April 9, 2020 8:53 AM Khem Raj <raj.khem@gmail.com> wrote:
> clang find an interesting failure
>
> 22:42:57 | main.c:116:2: error: embedding a #include directive within macro
> arguments is not supported
> 22:42:57 | #include "synopsis.c"
> 22:42:57 | ^
Interesting indeed. This is not my sode, I am just using it in openBMC.
Is this something what prevents integration?
--
Best regards,
Przemysław Czarnowski
[-- Attachment #2: Type: text/html, Size: 38045 bytes --]
next prev parent reply other threads:[~2020-04-10 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 23:39 [PATCH v2] Add nbdkit to extend backend possibilities of nbd Przemyslaw Czarnowski
2020-04-09 6:53 ` [oe] " Khem Raj
2020-04-10 10:17 ` przemyslaw.hawrylewicz.czarnowski [this message]
2020-04-11 22:26 ` Khem Raj
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=7592.1586513853636817343@lists.openembedded.org \
--to=przemyslaw.hawrylewicz.czarnowski@linux.intel.com \
--cc=openembedded-devel@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.