All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	ralf@linux-mips.org, linux-wireless@vger.kernel.org,
	linux-mips@linux-mips.org, jonas.gorski@gmail.com, mb@bu3sch.de,
	george@znau.edu.ua, arend@broadcom.com,
	b43-dev@lists.infradead.org, bernhardloos@googlemail.com,
	arnd@arndb.de, julian.calaby@gmail.com, sshtylyov@mvista.com
Subject: [PATCH v2 00/11] bcma: add support for embedded devices like bcm4716
Date: Fri, 22 Jul 2011 17:04:41 +0200	[thread overview]
Message-ID: <4E299189.7080700@hauke-m.de> (raw)
In-Reply-To: <20110722133925.GA10938@tuxdriver.com>

On 07/22/2011 03:39 PM, John W. Linville wrote:
> On Fri, Jul 22, 2011 at 10:24:00AM +0200, Hauke Mehrtens wrote:
>> On 07/22/2011 12:30 AM, Rafa? Mi?ecki wrote:
>>> 2011/7/16 Hauke Mehrtens <hauke@hauke-m.de>:
> 
>>>> @Ralf: Could you please merger this into the mips tree so that it will be in linux-3.1.
>>>
>>> ML for bcma is linux-wireless. Should we pass that patches "via" Ralf
>>> or John? Using linux-wireless (and John's tree) makes more sense to
>>> me, as we will work on the same tree and will get less merge
>>> conflicts. However don't take me as Linux development style guru, just
>>> my POV.
> 
>> I talked about this with Florian Fainelli and he said that the patches
>> should rather pass Ralf then John, but merging would be easier when they
>> are passing John. I do not have a problem with both solutions and
>> rebasing it to an other tree is no problem for me.
>> John and Ralf, who wants to take these patches? ;-)
> 
> I don't really care -- I figured Ralf was taking them due to the MIPS arch bits.
> 
> John

Hi John,

yes because of the MIPS arch bits it should go through Ralf, but there
are many changes for bcma in wireless-testing and adding my changes to
mips tree will cause some problems when wireless-testing and mips are
merged together by Linus.

Hauke

WARNING: multiple messages have this Message-ID (diff)
From: Hauke Mehrtens <hauke@hauke-m.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	ralf@linux-mips.org, linux-wireless@vger.kernel.org,
	linux-mips@linux-mips.org, jonas.gorski@gmail.com, mb@bu3sch.de,
	george@znau.edu.ua, arend@broadcom.com,
	b43-dev@lists.infradead.org, bernhardloos@googlemail.com,
	arnd@arndb.de, julian.calaby@gmail.com, sshtylyov@mvista.com
Subject: Re: [PATCH v2 00/11] bcma: add support for embedded devices like bcm4716
Date: Fri, 22 Jul 2011 17:04:41 +0200	[thread overview]
Message-ID: <4E299189.7080700@hauke-m.de> (raw)
In-Reply-To: <20110722133925.GA10938@tuxdriver.com>

On 07/22/2011 03:39 PM, John W. Linville wrote:
> On Fri, Jul 22, 2011 at 10:24:00AM +0200, Hauke Mehrtens wrote:
>> On 07/22/2011 12:30 AM, Rafał Miłecki wrote:
>>> 2011/7/16 Hauke Mehrtens <hauke@hauke-m.de>:
> 
>>>> @Ralf: Could you please merger this into the mips tree so that it will be in linux-3.1.
>>>
>>> ML for bcma is linux-wireless. Should we pass that patches "via" Ralf
>>> or John? Using linux-wireless (and John's tree) makes more sense to
>>> me, as we will work on the same tree and will get less merge
>>> conflicts. However don't take me as Linux development style guru, just
>>> my POV.
> 
>> I talked about this with Florian Fainelli and he said that the patches
>> should rather pass Ralf then John, but merging would be easier when they
>> are passing John. I do not have a problem with both solutions and
>> rebasing it to an other tree is no problem for me.
>> John and Ralf, who wants to take these patches? ;-)
> 
> I don't really care -- I figured Ralf was taking them due to the MIPS arch bits.
> 
> John

Hi John,

yes because of the MIPS arch bits it should go through Ralf, but there
are many changes for bcma in wireless-testing and adding my changes to
mips tree will cause some problems when wireless-testing and mips are
merged together by Linus.

Hauke

  reply	other threads:[~2011-07-22 15:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 16:55 [PATCH v2 00/11] bcma: add support for embedded devices like bcm4716 Hauke Mehrtens
2011-07-16 16:55 ` Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 01/11] bcma: move parsing of EEPROM into own function Hauke Mehrtens
2011-07-21 23:01   ` Rafał Miłecki
2011-07-21 23:01     ` Rafał Miłecki
2011-07-16 16:55 ` [PATCH v2 02/11] bcma: move initializing of struct bcma_bus to " Hauke Mehrtens
2011-07-21 23:01   ` Rafał Miłecki
2011-07-21 23:01     ` Rafał Miłecki
2011-07-16 16:55 ` [PATCH v2 03/11] bcma: add functions to scan cores needed on SoCs Hauke Mehrtens
2011-07-21 22:35   ` Rafał Miłecki
2011-07-21 22:35     ` Rafał Miłecki
2011-07-21 23:04     ` Rafał Miłecki
2011-07-21 23:04       ` Rafał Miłecki
2011-07-16 16:55 ` [PATCH v2 04/11] bcma: add SOC bus Hauke Mehrtens
2011-07-21 23:20   ` Rafał Miłecki
2011-07-21 23:20     ` Rafał Miłecki
2011-07-16 16:55 ` [PATCH v2 05/11] bcma: add mips driver Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 06/11] bcma: add serial console support Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 07/11] bcma: get CPU clock Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 08/11] bcm47xx: prepare to support different buses Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 09/11] bcm47xx: make it possible to build bcm47xx without ssb Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 10/11] bcm47xx: add support for bcma bus Hauke Mehrtens
2011-07-16 16:55 ` [PATCH v2 11/11] bcm47xx: fix irq assignment for new SoCs Hauke Mehrtens
2011-07-21 22:30 ` [PATCH v2 00/11] bcma: add support for embedded devices like bcm4716 Rafał Miłecki
2011-07-21 22:30   ` Rafał Miłecki
2011-07-22  8:24   ` Hauke Mehrtens
2011-07-22  8:24     ` Hauke Mehrtens
2011-07-22 13:39     ` John W. Linville
2011-07-22 13:39       ` John W. Linville
2011-07-22 15:04       ` Hauke Mehrtens [this message]
2011-07-22 15:04         ` Hauke Mehrtens
2011-07-22 20:16         ` John W. Linville
2011-07-22 20:16           ` John W. Linville

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=4E299189.7080700@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=arend@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=b43-dev@lists.infradead.org \
    --cc=bernhardloos@googlemail.com \
    --cc=george@znau.edu.ua \
    --cc=jonas.gorski@gmail.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=ralf@linux-mips.org \
    --cc=sshtylyov@mvista.com \
    --cc=zajec5@gmail.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.