All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Lang Daniel <d.lang@abatec.at>,
	Andrey Grafin <conquistador@yandex-team.ru>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/swupdate: fix ipc header include
Date: Thu, 10 Aug 2023 00:06:23 +0200	[thread overview]
Message-ID: <20230810000623.210176d4@windsurf> (raw)
In-Reply-To: <20230801002907.01f46d94@windsurf>

On Tue, 1 Aug 2023 00:29:07 +0200
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:

> So I would be inclined to do what upstream suggests here and drop the
> INCLUDEDIR=/usr/include/swupdate from swupdate.mk.
> 
> Thoughts?

Following the discussion we had, I submitted:

  https://patchwork.ozlabs.org/project/buildroot/patch/20230809220514.2089980-1-thomas.petazzoni@bootlin.com/

And I marked this patch proposed by Daniel Lang as Rejected. Let me
know what you think of this other proposal.

Thanks,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-09 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-02  9:26 [Buildroot] [PATCH] package/swupdate: fix ipc header include Lang Daniel via buildroot
2023-07-31 22:29 ` Thomas Petazzoni via buildroot
2023-08-09 22:06   ` Thomas Petazzoni via buildroot [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=20230810000623.210176d4@windsurf \
    --to=buildroot@buildroot.org \
    --cc=conquistador@yandex-team.ru \
    --cc=d.lang@abatec.at \
    --cc=thomas.petazzoni@bootlin.com \
    /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.