From: Paul Mundt <lethal@linux-sh.org>
To: Peter Huewe <PeterHuewe@gmx.de>
Cc: Matt Fleming <matt@console-pimps.org>,
Francesco Virlinzi <francesco.virlinzi@st.com>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/sh: Fix build failure caused by missing semicolon / missing include
Date: Mon, 18 Jan 2010 13:02:53 +0900 [thread overview]
Message-ID: <20100118040253.GA13854@linux-sh.org> (raw)
In-Reply-To: <201001180357.31594.PeterHuewe@gmx.de>
On Mon, Jan 18, 2010 at 03:57:31AM +0100, Peter Huewe wrote:
> From: Peter Huewe <peterhuewe@gmx.de>
> Date: Mon, 18 Jan 2010 03:48:31 +0100
>
> This patch fixes a build failure[1][2] for all sh configs, by fixing a
> missing semicolon and a missing include file.
>
> Build failure was introduced by the patch
> sh: fixed PMB mode refactoring [3]
> of Wed, 13 Jan 2010 09:31:48 +0000 (18:31 +0900)
>
This was already caught and corrected, thanks anyways.
prev parent reply other threads:[~2010-01-18 4:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 2:57 [PATCH] arch/sh: Fix build failure caused by missing semicolon / missing include Peter Huewe
2010-01-18 4:02 ` Paul Mundt [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=20100118040253.GA13854@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=PeterHuewe@gmx.de \
--cc=francesco.virlinzi@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=matt@console-pimps.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox