From: Ben Dooks <ben-linux@fluff.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Ben Dooks <ben-linux@fluff.org>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/5] h1940: fix h1940-bluetooth compilation
Date: Sun, 26 Sep 2010 00:39:43 +0100 [thread overview]
Message-ID: <4C9E883F.1010608@fluff.org> (raw)
In-Reply-To: <1283871605-32068-3-git-send-email-anarsoul@gmail.com>
On 07/09/10 16:00, Vasily Khoruzhick wrote:
> h1940-bluetooth.c doesn't compile after s3c gpio API changes,
> this patch fixes issue.
As a note, in future it would be very useful to have the part
of the build output showing the failure when submitting a
bug fix like this.
WARNING: multiple messages have this Message-ID (diff)
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] h1940: fix h1940-bluetooth compilation
Date: Sun, 26 Sep 2010 00:39:43 +0100 [thread overview]
Message-ID: <4C9E883F.1010608@fluff.org> (raw)
In-Reply-To: <1283871605-32068-3-git-send-email-anarsoul@gmail.com>
On 07/09/10 16:00, Vasily Khoruzhick wrote:
> h1940-bluetooth.c doesn't compile after s3c gpio API changes,
> this patch fixes issue.
As a note, in future it would be very useful to have the part
of the build output showing the failure when submitting a
bug fix like this.
next prev parent reply other threads:[~2010-09-25 23:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 15:00 [PATCH 0/5] h1940 series Vasily Khoruzhick
2010-09-07 15:00 ` Vasily Khoruzhick
2010-09-07 15:00 ` [PATCH 1/5] h1940: use gpiolib for latch access Vasily Khoruzhick
2010-09-07 15:00 ` Vasily Khoruzhick
2010-09-07 23:13 ` Ben Dooks
2010-09-07 23:13 ` Ben Dooks
2010-09-08 9:39 ` [PATCH v2 " Vasily Khoruzhick
2010-09-08 9:39 ` Vasily Khoruzhick
2010-09-07 15:00 ` [PATCH 2/5] h1940: fix h1940-bluetooth compilation Vasily Khoruzhick
2010-09-07 15:00 ` Vasily Khoruzhick
2010-09-25 23:22 ` Ben Dooks
2010-09-25 23:22 ` Ben Dooks
2010-09-25 23:39 ` Ben Dooks [this message]
2010-09-25 23:39 ` Ben Dooks
2010-09-07 15:00 ` [PATCH 3/5] h1940: implement mmc_power function Vasily Khoruzhick
2010-09-07 15:00 ` Vasily Khoruzhick
2010-09-25 23:43 ` Ben Dooks
2010-09-25 23:43 ` Ben Dooks
2010-09-26 21:27 ` [PATCH v2 " Vasily Khoruzhick
2010-09-26 21:27 ` Vasily Khoruzhick
2010-09-07 15:00 ` [PATCH 4/5] h1940: Fix backlight and LCD power functions Vasily Khoruzhick
2010-09-07 15:00 ` Vasily Khoruzhick
2010-09-11 21:45 ` [PATCH v2 " Vasily Khoruzhick
2010-09-11 21:45 ` Vasily Khoruzhick
2010-09-26 23:15 ` Ben Dooks
2010-09-26 23:15 ` Ben Dooks
2010-09-27 6:28 ` [PATCH v3 " Vasily Khoruzhick
2010-09-27 6:28 ` Vasily Khoruzhick
2010-09-07 23:14 ` [PATCH 0/5] h1940 series Ben Dooks
2010-09-07 23:14 ` Ben Dooks
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=4C9E883F.1010608@fluff.org \
--to=ben-linux@fluff.org \
--cc=anarsoul@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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.