Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org, Michael Buesch <mb@bu3sch.de>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH 1/6] [MIPS] BCM47xx: Add platform specific PCI code
Date: Thu, 25 Sep 2008 13:24:30 -0400	[thread overview]
Message-ID: <20080925172429.GB3277@tuxdriver.com> (raw)
In-Reply-To: <48DB6258.8010506@ru.mvista.com>

On Thu, Sep 25, 2008 at 02:05:12PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> John W. Linville wrote:
>
>> From: Aurelien Jarno <aurelien@aurel32.net>
>>
>> This patch, ported from OpenWRT SVN, defines pcibios_map_irq() and
>> pcibios_plat_dev_init() for the BCM47xx platform.
>>
>> It fixes the regression introduced by commit
>> aab547ce0d1493d400b6468c521a0137cd8c1edf ("ssb: Add Gigabit Ethernet
>> driver").
>>
>> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
>> Reviewed-by: Michael Buesch <mb@bu3sch.de>
>> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>>   
>
>   Thanks for addessing my nitpicking (which you could have ignored :-).
>   I'm only seeing this patch posted on April 21st before yesterday (and  
> receiving no comments) -- probably Aurilen hasn't been persevering  
> enough for Ralf to merge it. I've been a victim of Ralf's  
> "forgetfullness" as well, so I can sympathise. :-)

Sergei, I'm sorry if I was rude to you.

Ralf, given the OpenWRT and SSB connection, I could probably merge
this series through my tree if you don't want to take it in yours
for some reason.

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  parent reply	other threads:[~2008-09-25 17:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 19:18 [PATCH 0/6] BCM47xx patches Aurelien Jarno
2008-09-24 19:19 ` [PATCH 1/6] [MIPS] BCM47xx: Add platform specific PCI code Aurelien Jarno
2008-09-24 21:17   ` Michael Buesch
2008-09-24 22:14   ` Sergei Shtylyov
2008-09-24 22:31     ` Michael Buesch
2008-09-25  0:14     ` John W. Linville
2008-09-25  9:54       ` Sergei Shtylyov
2008-09-25  0:18     ` John W. Linville
2008-09-25  0:18       ` John W. Linville
2008-09-25 10:05       ` Sergei Shtylyov
2008-09-25 12:32         ` Aurelien Jarno
2008-09-25 14:39           ` Sergei Shtylyov
2008-09-25 20:59             ` Michael Buesch
2008-09-25 17:24         ` John W. Linville [this message]
2008-09-25 21:00           ` Michael Buesch
2008-09-26 15:42     ` Ralf Baechle
2008-09-26 18:23   ` [PATCH 1/6 v2] " Aurelien Jarno
2008-09-27 14:06     ` [PATCH 1/6 v3] " Aurelien Jarno
2008-09-27 14:35       ` Ralf Baechle
2008-09-24 19:20 ` [PATCH 2/6] [MIPS] WGT634U: Add machine detection message Aurelien Jarno
2008-09-24 19:21 ` [PATCH 3/6] [MIPS] Remove references to BCM947XX Aurelien Jarno
2008-09-24 19:22 ` [PATCH 4/6] [MIPS] BCM47xx: Use the new SSB GPIO API Aurelien Jarno
2008-09-24 19:23 ` [PATCH 5/6] [MIPS] Add WGT634U reset button support Aurelien Jarno
2008-09-24 19:23 ` [PATCH 6/6] [MIPS] Scan PCI busses when they are registered Aurelien Jarno

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=20080925172429.GB3277@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=aurelien@aurel32.net \
    --cc=linux-mips@linux-mips.org \
    --cc=mb@bu3sch.de \
    --cc=ralf@linux-mips.org \
    --cc=sshtylyov@ru.mvista.com \
    /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