From: Olof Johansson <olof@lixom•net>
To: Timur Tabi <timur@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] Add information on enabling sound on the MPC8641 HPCN
Date: Sun, 23 Dec 2007 09:26:13 -0600 [thread overview]
Message-ID: <20071223152613.GA4817@lixom.net> (raw)
In-Reply-To: <11983809443854-git-send-email-timur@freescale.com>
On Sat, Dec 22, 2007 at 09:35:44PM -0600, Timur Tabi wrote:
> Add a comment to the DTS file for the MPC8641 HPCN describing a wiring change
> needed to get sound working on this board.
>
> Signed-off-by: Timur Tabi <timur@freescale•com>
> ---
>
> For a two-line comment, I thought the DTS would be the best place to put this
> information.
Sounds like a board rework document on your support site is the right
place for this. We normally don't document board reworks required in
the linux sources, do we?
-Olof
next prev parent reply other threads:[~2007-12-23 15:19 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 [this message]
2007-12-24 17:24 ` Timur Tabi
2007-12-24 23:10 ` Olof Johansson
2007-12-25 20:42 ` Timur Tabi
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=20071223152613.GA4817@lixom.net \
--to=olof@lixom$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=timur@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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