From: mushtaq khan <mushtaq_k@procsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Sata patch with respect to uboot testing repository
Date: Mon, 25 Jun 2007 10:30:06 +0530 [thread overview]
Message-ID: <467F4BD6.8060100@procsys.com> (raw)
In your mail you had written:
The patch was checked in, so now you are supposed
to test the resulting code and provide feedback
Best regards,
Wolfgang Denk
Hi Wolfgang,
You have not applied the sata patch to your u-boot-testing repository. I
downloaded u-boot-testing code from your testing repository
git://www.denx.de/git/u-boot-testing
And i couldn't find my changes, Please apply the sata patch to your
testing repository. For your convenience iam attaching the sata patch
with the mail.
This sata patch is with respect to u-boot-testing repository, which
resolves the prototype mismatch between sata_read and block_read.
Thanks,
-Mushtaq
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sata_utest.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20070625/6a1ecf93/attachment.txt
reply other threads:[~2007-06-25 5:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=467F4BD6.8060100@procsys.com \
--to=mushtaq_k@procsys.com \
--cc=u-boot@lists.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