From: Ralf Baechle <ralf@linux-mips.org>
To: Wolfgang Ocker <weo@reccoware.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] [MIPS] Fix ids in Alchemy db dma device table (Repost in hopefully correct format)
Date: Wed, 20 Feb 2008 12:59:19 +0000 [thread overview]
Message-ID: <20080220125919.GA24984@linux-mips.org> (raw)
In-Reply-To: <1202671893.3384.20.camel@galileo.recco.de>
On Sun, Feb 10, 2008 at 08:31:33PM +0100, Wolfgang Ocker wrote:
> Subject: [PATCH] [MIPS] Fix ids in Alchemy db dma device table (Repost in
> hopefully correct format)
> Content-Type: text/plain
>
> From: Wolfgang Ocker <weo@reccoware.de>
Kudos for resending in The Right Format (TM) before I had a chance to beg
for it :-) It seems though you were generating an unclean or maybe simply
older version of the tree to generate this patch. Git didn't like it and
patch only with fuzz.
Applied,
Ralf
prev parent reply other threads:[~2008-02-20 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 19:31 [PATCH] [MIPS] Fix ids in Alchemy db dma device table (Repost in hopefully correct format) Wolfgang Ocker
2008-02-20 12:59 ` Ralf Baechle [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=20080220125919.GA24984@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=weo@reccoware.de \
/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