Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Raghavan <arun.raghavan@collabora.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-utils] [PATCH 1/3] aplay: Fix signal.h include
Date: Wed, 18 Jul 2012 11:29:43 +0530	[thread overview]
Message-ID: <1342591183.5405.4.camel@localhost> (raw)
In-Reply-To: <s5hd33ulehg.wl%tiwai@suse.de>

On Tue, 2012-07-17 at 15:11 +0200, Takashi Iwai wrote:
> At Tue, 17 Jul 2012 15:45:33 +0530,
> Arun Raghavan wrote:
> > 
> > The correct header to include is <signal.h> not <sys/signal.h>.
> 
> Applied all now despite of lack of sign-off, as these are so trivial
> patches.

Thanks! Will try to make sure I don't forget in the future.

-- Arun

      reply	other threads:[~2012-07-18  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 10:15 [alsa-utils] [PATCH 1/3] aplay: Fix signal.h include Arun Raghavan
2012-07-17 10:15 ` [alsa-utils] [PATCH 2/3] aplay: Use open() instead of open64() Arun Raghavan
2012-07-17 10:15 ` [alsa-utils] [PATCH 3/3] build: Don't call AC_CHECK_FUNC with --disable-alsatest Arun Raghavan
2012-07-17 13:11 ` [alsa-utils] [PATCH 1/3] aplay: Fix signal.h include Takashi Iwai
2012-07-18  5:59   ` Arun Raghavan [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=1342591183.5405.4.camel@localhost \
    --to=arun.raghavan@collabora.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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