From: Timur Tabi <timur@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Add information on enabling sound on the MPC8641 HPCN
Date: Tue, 25 Dec 2007 14:42:34 -0600 [thread overview]
Message-ID: <47716B3A.9050008@freescale.com> (raw)
In-Reply-To: <20071224231042.GA4588@lixom.net>
Olof Johansson wrote:
> Are freescale customers really used to going to the linux device tree
> sources to find out how to modify their boards to achieve certain
> functionality with their eval boards?! I guess you guys are taking the
> "device trees are used to describe the hardware" statement to it's
> fullest extent.
Well, I've always been a rebel.
Honestly, I just thought it would be harmless and a lot easier (for me)
than trying to convince some documentation dude to write it up and
publish it.
next prev parent reply other threads:[~2007-12-25 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-23 3:35 [PATCH] Add information on enabling sound on the MPC8641 HPCN Timur Tabi
2007-12-23 15:26 ` Olof Johansson
2007-12-24 17:24 ` Timur Tabi
2007-12-24 23:10 ` Olof Johansson
2007-12-25 20:42 ` Timur Tabi [this message]
2007-12-26 2:18 ` Olof Johansson
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=47716B3A.9050008@freescale.com \
--to=timur@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).