From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Make raumfeld.c compile
Date: Wed, 13 Jan 2010 13:46:43 +0100 [thread overview]
Message-ID: <20100113124643.GC9007@buzzloop.caiaq.de> (raw)
In-Reply-To: <f17812d71001130411g2293ea3l13f22637ef614f9b@mail.gmail.com>
On Wed, Jan 13, 2010 at 08:11:26PM +0800, Eric Miao wrote:
> On Wed, Jan 13, 2010 at 8:03 PM, Daniel Mack <daniel@caiaq.de> wrote:
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Eric Miao <eric.y.miao@gmail.com>
> > ---
> > Eric, as the original patch isn't merged yet, you can also squash this one
> > if you like, whatever works better for you.
> >
>
> I've already corrected that one. Are you able to give a quick test of
> my 'devel' branch, it's there except not pulled.
Ah, great, missed that.
Your devel branch works well for me, thanks a lot.
Daniel
prev parent reply other threads:[~2010-01-13 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 12:03 [PATCH] ARM: Make raumfeld.c compile Daniel Mack
2010-01-13 12:11 ` Eric Miao
2010-01-13 12:46 ` Daniel Mack [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=20100113124643.GC9007@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).