From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: tiwai@suse.de, rmk+lkml@arm.linux.org.uk, wli@holomorphy.com,
davem@davemloft.net, torvalds@osdl.org, nickpiggin@yahoo.com.au,
airlied@gmail.com, linux-kernel@vger.kernel.org,
alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH 12/11] unpaged: fix sound Bad page states
Date: Mon, 21 Nov 2005 12:41:05 -0800 [thread overview]
Message-ID: <20051121124105.1bf8090d.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0511211801070.17464@goblin.wat.veritas.com>
Hugh Dickins <hugh@veritas.com> wrote:
>
> arch/sparc/kernel/ioport.c | 2 +-
> arch/sparc64/kernel/sbus.c | 2 +-
> sound/core/memalloc.c | 2 ++
> 3 files changed, 4 insertions(+), 2 deletions(-)
So with this, do you think everything is in place for a mainline merge?
next prev parent reply other threads:[~2005-11-21 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 18:12 [PATCH 12/11] unpaged: fix sound Bad page states Hugh Dickins
2005-11-21 20:41 ` Andrew Morton [this message]
2005-11-21 22:40 ` Hugh Dickins
2005-11-21 21:57 ` William Lee Irwin III
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=20051121124105.1bf8090d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=airlied@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=tiwai@suse.de \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.com \
/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