From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Rupjyoti Sarmah <rsarmah@amcc.com>
Cc: linux-ide@vger.kernel.org, sr@denx.de, rsarmah@apm.com,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH]Device tree update for the 460ex DWC SATA<resubmission>
Date: Sun, 6 Jun 2010 14:47:48 -0400 [thread overview]
Message-ID: <20100606184748.GC7801@zod.rchland.ibm.com> (raw)
In-Reply-To: <201006041003.o54A3CIi024533@amcc.com>
On Fri, Jun 04, 2010 at 03:33:12PM +0530, Rupjyoti Sarmah wrote:
>
>Device tree update for the Applied micro processor 460ex on-chip SATA
>Signed-off-by: Rupjyoti Sarmah <rsarmah@amcc.com>
You sent this same patch twice. Mistake, or was there supposed to be a
difference?
josh
next prev parent reply other threads:[~2010-06-06 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 10:03 [PATCH]Device tree update for the 460ex DWC SATA<resubmission> Rupjyoti Sarmah
2010-06-06 18:47 ` Josh Boyer [this message]
2010-06-07 4:56 ` Rupjyoti Sarmah
-- strict thread matches above, loose matches on Subject: below --
2010-06-04 8:04 Rupjyoti Sarmah
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=20100606184748.GC7801@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rsarmah@amcc.com \
--cc=rsarmah@apm.com \
--cc=sr@denx.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;
as well as URLs for NNTP newsgroup(s).