From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] perl-sys-cpu: remove extraneous include
Date: Mon, 8 Oct 2018 21:57:06 +0200 [thread overview]
Message-ID: <20181008215706.0a196d99@windsurf> (raw)
In-Reply-To: <20180927144646.20954-3-chrismcc@gmail.com>
Hello,
On Thu, 27 Sep 2018 07:46:46 -0700, Christopher McCrory wrote:
> remove extraneous include <sys/unistd.h>
> in glibc this points back to include unistd.h
> neither musl, nor uclib have it.
>
> Signed-off-by: Christopher McCrory <chrismcc@gmail.com>
The patch below was missing a description, and the commit log was
lacking a reference to the autobuilder failure being fixed. I've fixed
both issues, and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-08 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:46 [Buildroot] [PATCH 0/2] perl-sys-cpu fixes Christopher McCrory
2018-09-27 14:46 ` [Buildroot] [PATCH 1/2] perl-sys-cpu: disable static builds Christopher McCrory
2018-10-08 19:56 ` Thomas Petazzoni
2018-09-27 14:46 ` [Buildroot] [PATCH 2/2] perl-sys-cpu: remove extraneous include Christopher McCrory
2018-10-08 19:57 ` Thomas Petazzoni [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=20181008215706.0a196d99@windsurf \
--to=thomas.petazzoni@bootlin.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