From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouanchristophe@gmail.com>
Cc: Heiko Thiery <heiko.thiery@gmail.com>,
Petr Kulhavy <brain@jikos.cz>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/linuxptp: bump to v4.0
Date: Mon, 10 Jul 2023 19:23:32 +0200 [thread overview]
Message-ID: <20230710192332.39cd7ef4@windsurf> (raw)
In-Reply-To: <20230630132912.128835-1-titouanchristophe@gmail.com>
On Fri, 30 Jun 2023 15:29:12 +0200
Titouan Christophe <titouanchristophe@gmail.com> wrote:
> - Drop patches that have been applied upstream
> - Drop hash that are not available on Soureforge anymore
>
> Signed-off-by: Titouan Christophe <titouanchristophe@gmail.com>
> ---
> ...g.h-drop-clock_nanosleep-replacement.patch | 49 -------------------
> ...itional-assignment-for-KBUILD_OUTPUT.patch | 43 ----------------
> package/linuxptp/linuxptp.hash | 6 +--
> package/linuxptp/linuxptp.mk | 2 +-
> 4 files changed, 2 insertions(+), 98 deletions(-)
> delete mode 100644 package/linuxptp/0001-missing.h-drop-clock_nanosleep-replacement.patch
> delete mode 100644 package/linuxptp/0002-makefile-use-conditional-assignment-for-KBUILD_OUTPUT.patch
Sorry, I'm seeing your patch only now, and I've applied another similar
patch from Jean-Michel Friedt in the mean time. Sorry about this :-/
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-10 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 13:29 [Buildroot] [PATCH 1/1] package/linuxptp: bump to v4.0 Titouan Christophe
2023-07-01 19:02 ` Heiko Thiery
2023-07-10 17:23 ` 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=20230710192332.39cd7ef4@windsurf \
--to=buildroot@buildroot.org \
--cc=brain@jikos.cz \
--cc=heiko.thiery@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouanchristophe@gmail.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.