From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [LIBFDT] Fixup byteswapping code
Date: Mon, 4 Dec 2006 12:53:29 +1100 [thread overview]
Message-ID: <20061204015329.GA4790@localhost.localdomain> (raw)
In-Reply-To: <11650491414017-git-send-email-grant.likely@secretlab.ca>
I just applied a patch with a whole batch of endian fixes, obsoleting
this patch of yours.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2006-12-04 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 8:45 [LIBFDT] Fixup byteswapping code Grant Likely
2006-12-02 8:45 ` [LIBFDT] Add .dtb files to .gitignore Grant Likely
2006-12-02 9:30 ` Segher Boessenkool
2006-12-04 0:19 ` David Gibson
2006-12-04 1:53 ` David Gibson [this message]
2006-12-04 5:18 ` [LIBFDT] Fixup byteswapping code Grant Likely
2006-12-04 5:52 ` David Gibson
2006-12-04 6:33 ` Grant Likely
2006-12-04 7:16 ` David Gibson
2006-12-04 14:55 ` Grant Likely
2006-12-08 6:09 ` David Gibson
2006-12-15 4:15 ` David Gibson
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=20061204015329.GA4790@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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).