From: Seth Forshee <seth.forshee@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH trace-cmd 1/5] trace-cmd/listen: Remove use of sighandler_t
Date: Thu, 24 Oct 2013 15:30:07 -0500 [thread overview]
Message-ID: <20131024203007.GB8006@thinkpad-t410> (raw)
In-Reply-To: <1382642074-15567-2-git-send-email-seth.forshee@canonical.com>
On Thu, Oct 24, 2013 at 02:14:30PM -0500, Seth Forshee wrote:
> sighandler_t is a GNU extension and may not be defined if
> _GNU_SOURCE is not set. To minimize the potential for build
> problems, change signal_setup() to declare its handle argument
> the same way struct sigaction declares the sa_handler member.
I just saw that you've already got a commit to define _GNU_SOURCE on
master. I was packaging v2.2.1 and didn't notice it, so you can ignore
this one.
next prev parent reply other threads:[~2013-10-24 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 19:14 [PATCH trace-cmd 0/5] Miscellaneous fixes for trace-cmd Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 1/5] trace-cmd/listen: Remove use of sighandler_t Seth Forshee
2013-10-24 20:30 ` Seth Forshee [this message]
2013-10-28 15:45 ` Seth Forshee
2013-11-01 13:40 ` Steven Rostedt
2013-10-24 19:14 ` [PATCH trace-cmd 2/5] build: Install data files without execute permissions Seth Forshee
2013-10-25 8:31 ` Steven Rostedt
2013-10-25 13:05 ` Seth Forshee
2013-10-25 13:42 ` Steven Rostedt
2013-10-24 19:14 ` [PATCH trace-cmd 3/5] Add missing libgen.h includes Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 4/5] Documentation: Add kernelshark.1.txt Seth Forshee
2013-11-11 6:54 ` Rob Landley
2013-11-11 13:47 ` Seth Forshee
2013-10-24 19:14 ` [PATCH trace-cmd 5/5] build: Use CFLAGS and LDFLAGS when building python bits Seth Forshee
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=20131024203007.GB8006@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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