alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH] Fix bint check version check
Date: Thu, 19 Jan 2012 16:41:03 +0100	[thread overview]
Message-ID: <4F18398F.20900@perex.cz> (raw)
In-Reply-To: <1326986710-12389-1-git-send-email-ozan@pardus.org.tr>

Date 19.1.2012 16:25, Ozan Çağlayan wrote:
> It seems that the bint stuff is not a part of 3.2 kernel as it's
> pulled by Linus only a few days ago, so increment version check
> to 3.3.0:

Thanks. Applied.

				Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2012-01-19 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 15:25 [PATCH] Fix bint check version check Ozan Çağlayan
2012-01-19 15:41 ` Jaroslav Kysela [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=4F18398F.20900@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=ozan@pardus.org.tr \
    --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;
as well as URLs for NNTP newsgroup(s).