public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel•crashing.org>
To: Chris Friesen <cfriesen@nortelnetworks•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: support for revision C of the mcpn765?
Date: Tue, 21 Sep 2004 16:15:42 -0700	[thread overview]
Message-ID: <20040921231542.GD16619@smtp.west.cox.net> (raw)
In-Reply-To: <414B6363.5060106@nortelnetworks.com>

On Fri, Sep 17, 2004 at 04:21:23PM -0600, Chris Friesen wrote:

> 
> We've got revision C of the mcpn765 from Motorola.  The main difference 
> appears to be that it uses the 82c686 chip rather than the 586, requiring 
> some extra checking in mcpn765_init2().
> 
> Is there a patch already out there, or should I send one in?

Please post a patch vs a current 2.6 (and if you haven't already, read
Documentation/SubmittingPatches and read the Developer's Certificate of
Origin).  Thanks.

-- 
Tom Rini
http://gate.crashing.org/~trini/

      reply	other threads:[~2004-09-21 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 22:21 support for revision C of the mcpn765? Chris Friesen
2004-09-21 23:15 ` Tom Rini [this message]

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=20040921231542.GD16619@smtp.west.cox.net \
    --to=trini@kernel$(echo .)crashing.org \
    --cc=cfriesen@nortelnetworks$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /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