From: Chen Gang <xili_gchen_5257@hotmail.com>
To: "Kalle Valo" <kvalo@codeaurora.org>, "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Arnd Bergmann" <arnd@arndb.de>,
"Jim Davis" <jim.epost@gmail.com>, "Michael Büsch" <m@bues.ch>
Subject: Re: [PATCH] bcma: Kconfig: Let it depend on PCI
Date: Fri, 6 Mar 2015 04:02:16 +0800 [thread overview]
Message-ID: <BLU436-SMTP255C4EA2EC2AD5F4A757276B91F0@phx.gbl> (raw)
In-Reply-To: <87r3t365aw.fsf@kamboji.qca.qualcomm.com>
On 3/5/15 19:40, Kalle Valo wrote:
> Rafał Miłecki <zajec5@gmail.com> writes:
>
>> Kalle, I guess the recent discussion and work on this problem could be
>> confusing, so let me try to sum it up it a bit.
>>
>> First of all, please note there are 3 awaiting bcma patches that
>> should be applied independently of what we decide to do with this
>> patch. They are of course inspired by the recent building problems.
>> List of these patches:
>> [PATCH next] bcma: make bcma_host_pci_(up|down) calls safe for every config
>> [PATCH next] bcma: move internal function declarations to private header
>> [PATCH next] bcma: prepare Kconfig symbol for PCI driver
>>
>> Now, the building problem is obviously caused by me, my work on
>> driver_pcie2.c and using pcie_set_readrq there without making sure
>> that is PCI available. I'm sorry for that.
>>
>> All 3 above patches are moving us toward the the most optimal solution
>> of this problem. Depending on PCI only when it's really required.
>> There is still one more change missing that I'm working on. It'll take
>> me about 2 more days to get the last patch.
>> On the other way, patch proposed by Chen fixes building problem right
>> now. It's much simpler but bumps bcma requirements a bit too high.
>> bcma doesn't really have to depend on PCI.
>
> Thanks for the good summary, it clarified things for me.
>
>> So you have 2 options there and I'll be happy with whatever you choose to do:
>> 1) Pick Chen patch now and in ~2 days apply my final fix + revert Chen
>> patch.
>
> I'll prefer this option so that we can quickly solve the build problem.
> Also once your final fix is ready, please remember that you need to
> revert Chen's patch within the same patch.
>
Thank you for all of your work. In honest, I am not quite familiar with
the details, my patch is applied only says that "I am lucky enough".
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2015-03-05 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 21:16 Chen Gang
2015-03-04 6:19 ` Rafał Miłecki
2015-03-04 12:08 ` Rafał Miłecki
2015-03-04 13:36 ` Rafał Miłecki
2015-03-04 16:38 ` Michael Büsch
2015-03-04 16:39 ` Rafał Miłecki
2015-03-04 7:41 ` Chen Gang
2015-03-04 22:23 ` Rafał Miłecki
2015-03-05 11:40 ` Kalle Valo
2015-03-05 20:02 ` Chen Gang [this message]
2015-03-05 11:57 ` Kalle Valo
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=BLU436-SMTP255C4EA2EC2AD5F4A757276B91F0@phx.gbl \
--to=xili_gchen_5257@hotmail.com \
--cc=arnd@arndb.de \
--cc=hauke@hauke-m.de \
--cc=jim.epost@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m@bues.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®