From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [GIT PULL] fixes for wrong DB_RANGE_HEADER sizes
Date: Sun, 20 Nov 2011 21:02:45 +0000 [thread overview]
Message-ID: <20111120210245.GD2976@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EC91ADF.30702@ladisch.de>
On Sun, Nov 20, 2011 at 04:21:03PM +0100, Clemens Ladisch wrote:
> The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:
>
> Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)
>
> are available in the git repository at:
> git://git.alsa-project.org/alsa-kprivate.git DB_RANGE-size-fixes
>
> Clemens Ladisch (7):
I'm sorry, I'm not going to pull this as I've never seen the patches and
you've not even described the issue you're trying to fix. Patches
should be sent even if there's a pull request and if for some reason you
skip that step the description in the pull request is important.
next prev parent reply other threads:[~2011-11-20 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 15:21 [GIT PULL] fixes for wrong DB_RANGE_HEADER sizes Clemens Ladisch
2011-11-20 21:02 ` Mark Brown [this message]
2011-11-20 21:56 ` Clemens Ladisch
2011-11-21 11:30 ` Mark Brown
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=20111120210245.GD2976@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.