From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, Alex Elder <elder@kernel.org>,
Axel Haslam <ahaslam@baylibre.com>,
Johan Hovold <johan@kernel.org>,
linux-kernel@vger.kernel.org, greybus-dev@lists.linaro.org
Subject: [PATCH 0/3] staging: greybus: loopback_test: fix build breakage
Date: Thu, 12 Mar 2020 12:01:48 +0100 [thread overview]
Message-ID: <20200312110151.22028-1-johan@kernel.org> (raw)
The loopback_test tool hasn't received much love lately. In fact, it has
failed to build for the past two years after a scripted EPOLL*
conversion.
Newer GCC also started warning for potential string truncation of
generated path names; the last two patches addresses that.
Johan
Johan Hovold (3):
staging: greybus: loopback_test: fix poll-mask build breakage
staging: greybus: loopback_test: fix potential path truncation
staging: greybus: loopback_test: fix potential path truncations
drivers/staging/greybus/tools/loopback_test.c | 21 ++++++++++---------
1 file changed, 11 insertions(+), 10 deletions(-)
--
2.24.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2020-03-12 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 11:01 Johan Hovold [this message]
2020-03-12 11:01 ` [PATCH 1/3] staging: greybus: loopback_test: fix poll-mask build breakage Johan Hovold
2020-03-12 11:01 ` [PATCH 2/3] staging: greybus: loopback_test: fix potential path truncation Johan Hovold
2020-03-12 11:01 ` [PATCH 3/3] staging: greybus: loopback_test: fix potential path truncations Johan Hovold
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=20200312110151.22028-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=ahaslam@baylibre.com \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).