From: Gabor Juhos <juhosg@openwrt.org>
To: "René Bolldorf" <xsecute@googlemail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Imre Kaloz <kaloz@openwrt.org>
Subject: Re: [PATCH 00/12] MIPS: ath79: AR724X PCI fixes and AR71XX PCI support
Date: Thu, 24 Nov 2011 19:39:39 +0100 [thread overview]
Message-ID: <4ECE8F6B.1060203@openwrt.org> (raw)
In-Reply-To: <CAEWqx59_YvRfqKxhTYAxrCh=W+UV89V5ibMnBQpC+2i-Ed08Kg@mail.gmail.com>
2011.11.24. 16:54 keltezéssel, René Bolldorf írta:
> 2011/11/24 Gabor Juhos <juhosg@openwrt.org>:
>> Hi René,
>>
>>> Sorry Gabor for the following patch, but it seems your patchset was
>>> against a other tree?
>>
>> Both of my patch sets was based on the 'mips-for-linux-next' branch of Ralf's
>> 'upstream-sfr' tree:
>>
>> git://git.linux-mips.org/pub/scm/ralf/upstream-sfr.git
>>
>>> Because of the many failures I rebase'ed against 09521577ca7718b6c of the
>>> linus tree and written anything from scratch.
>>
>> That was waste of time. The ath79 platform got a pile of changes recently, and
>> those changes are not yet available in Linus' tree. If you were unsure about the
>> tree, you should have asked earlier.
>>
>
> Alright. I don't play with all trees now.
Why if not indiscreet?
> I wait for the next merge.
If you mean Linus' tree, the new codes will not be merged into that before the
release of 3.2. You would have to wait for a few weeks probably.
-Gabor
next prev parent reply other threads:[~2011-11-24 18:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 23:14 [PATCH 00/12] MIPS: ath79: AR724X PCI fixes and AR71XX PCI support Gabor Juhos
2011-11-22 23:14 ` [PATCH 01/12] MIPS: ath79: remove superfluous alignment checks from pci-ar724x.c Gabor Juhos
2011-11-22 23:14 ` [PATCH 02/12] MIPS: ath79: fix broken ar724x_pci_{read,write} functions Gabor Juhos
2011-11-22 23:14 ` [PATCH 03/12] MIPS: ath79: add a workaround for a PCI controller bug in AR724X SoCs Gabor Juhos
2011-11-22 23:14 ` [PATCH 04/12] MIPS: ath79: fix a wrong IRQ number Gabor Juhos
2011-11-22 23:14 ` [PATCH 05/12] MIPS: ath79: add PCI IRQ handling code for AR724X SoCs Gabor Juhos
2011-11-22 23:14 ` [PATCH 06/12] MIPS: ath79: get rid of some ifdefs in mach-ubnt-xm.c Gabor Juhos
2011-11-22 23:14 ` [PATCH 07/12] MIPS: ath79: allow to use board specific pci_plat_dev_init functions Gabor Juhos
2011-11-22 23:14 ` [PATCH 08/12] MIPS: ath79: add support for the PCI host controller of the AR71XX SoCs Gabor Juhos
2011-11-23 9:21 ` Sergei Shtylyov
2011-11-23 12:04 ` Gabor Juhos
2011-11-22 23:14 ` [PATCH 09/12] MIPS: ath79: allow to use SoC specific PCI IRQ maps Gabor Juhos
2011-11-22 23:14 ` [PATCH 10/12] MIPS: ath79: remove ar724x_pci_add_data function Gabor Juhos
2011-11-22 23:14 ` [PATCH 11/12] MIPS: ath79: register PCI controller on the PB44 board Gabor Juhos
2011-11-22 23:14 ` [PATCH 12/12] MIPS: ath79: update copyright headers of PCI related files Gabor Juhos
2011-11-23 11:35 ` [PATCH 00/12] MIPS: ath79: AR724X PCI fixes and AR71XX PCI support René Bolldorf
2011-11-23 14:08 ` Gabor Juhos
2011-11-23 14:40 ` René Bolldorf
2011-11-23 15:15 ` René Bolldorf
2011-11-23 20:43 ` Gabor Juhos
2011-11-24 10:37 ` René Bolldorf
2011-11-24 15:06 ` Gabor Juhos
2011-11-24 15:54 ` René Bolldorf
2011-11-24 18:39 ` Gabor Juhos [this message]
2011-11-23 20:39 ` Gabor Juhos
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=4ECE8F6B.1060203@openwrt.org \
--to=juhosg@openwrt.org \
--cc=kaloz@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=xsecute@googlemail.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 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.