From: Tejun Heo <tj@kernel.org>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Neil Horman <nhorman@tuxdriver.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] speakup: fakekey.c: Fix error: macro "__this_cpu_write" requires 2 arguments, but only 1 given
Date: Wed, 08 Dec 2010 14:59:13 +0100 [thread overview]
Message-ID: <4CFF8F31.4010507@kernel.org> (raw)
In-Reply-To: <AANLkTim0-EY8z6_XYG9ZGc3RnK7v8Du4njygsH62Wc5M@mail.gmail.com>
On 12/08/2010 02:38 PM, Sedat Dilek wrote:
> While building linux-next (next-20101208) I fell over this build failure.
> The attached patch is compile-tested-only.
Rolled into the original patch. Thank you very much for catching it.
--
tejun
prev parent reply other threads:[~2010-12-08 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 13:38 [PATCH] speakup: fakekey.c: Fix error: macro "__this_cpu_write" requires 2 arguments, but only 1 given Sedat Dilek
2010-12-08 13:59 ` Tejun Heo [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=4CFF8F31.4010507@kernel.org \
--to=tj@kernel.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=schwidefsky@de.ibm.com \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--cc=sfr@canb.auug.org.au \
/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