All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>, clem.taylor@gmail.com
Subject: Re: I2C troubles with Au1550
Date: Fri, 19 May 2006 21:11:10 +0400	[thread overview]
Message-ID: <446DFC2E.4040400@ru.mvista.com> (raw)
In-Reply-To: <20060519150851.GD9596@cosmic.amd.com>

Jordan Crouse wrote:
> On 19/05/06 18:48 +0400, Sergei Shtylyov wrote:
>  
> 
>>   Alas, I have to NAK this. DBAu1200 code should be in 
>>arch/mips/au1000/pb1200/...

> if this was DB1200 code only, I would be inclined to agree, but its
> not - so this code is well placed.

    It's under #ifdef CONFIG_MIPS_DB1200, so is *completely* misplaced. This 
file is not even compiled for DBAu1200. Therefore, this code will never execute.

>>   Thou wait... that hunk won't even aplly to the current git tree... 

> Well, it does apply - latest GIT tree, right from l-m.o

    Hmm, indeed it applies with fuzz (because of PSC redefinitions)... So, I'm 
taking this back. :-)

>>Looks like this patch is trying to redeclare PSC base addresses for Au1200 

> Yeah, it does a redundant declaration - I'll pull that part of it.  The
> rest of the patch is still valid though - I see no reason why you should NAK
> it, especially when this was posted by popular request.

    Because I caught a defect in it with naked eye. Maybe NAKing it was indeed 
too much. :-)

> Jordan

MBR, Sergei

  reply	other threads:[~2006-05-19 18:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 21:54 I2C troubles with Au1550 Clem Taylor
2006-05-19 14:32 ` Jordan Crouse
2006-05-19 14:48   ` Sergei Shtylyov
2006-05-19 15:08     ` Jordan Crouse
2006-05-19 17:11       ` Sergei Shtylyov [this message]
2006-05-19 15:14     ` Ralf Baechle
2006-05-19 15:00   ` Sergei Shtylyov

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=446DFC2E.4040400@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=clem.taylor@gmail.com \
    --cc=jordan.crouse@amd.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.