From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] package/ltp-testsuite: proper fix for missing __kernel_fsid_t
Date: Sun, 17 Nov 2019 10:24:34 +0100 [thread overview]
Message-ID: <20191117092434.GA22986@x230> (raw)
In-Reply-To: <20191116094220.GC32494@scaer>
Hi Yann,
> [--SNIP--]
> > [1] https://patchwork.ozlabs.org/patch/1195915/
> I've added this URL to the description of patch 7, and applied to
> master, thanks.
Thanks! I'll probably merge patch [1] in LTP on Monday (already Acked by Jan
Stancek, pretty obvious, but I'll prefer to wait Cyril Hrubis ack).
Not sure if it's worth then add commit hash in buildroot patch and renumber
patches (0005 was already taken by static linking fix), I guess these are minor
and not needed to be done. Anyway, these are 3 are backports thus temporary.
Kind regards,
Petr
prev parent reply other threads:[~2019-11-17 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:36 [Buildroot] [PATCH v3 1/1] package/ltp-testsuite: proper fix for missing __kernel_fsid_t Petr Vorel
2019-11-16 9:42 ` Yann E. MORIN
2019-11-17 9:24 ` Petr Vorel [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=20191117092434.GA22986@x230 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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