From: Kalle Valo <kvalo@codeaurora.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: "kbuild test robot" <lkp@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
"Luis de Bethencourt" <luisbg@osg.samsung.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcma: mips: Allow build if COMPILE_TEST is enabled
Date: Wed, 14 Oct 2015 14:04:08 +0300 [thread overview]
Message-ID: <87h9ltn23b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <561E3481.4070008@osg.samsung.com> (Javier Martinez Canillas's message of "Wed, 14 Oct 2015 12:54:57 +0200")
Javier Martinez Canillas <javier@osg.samsung.com> writes:
> On 10/14/2015 12:52 PM, Kalle Valo wrote:
>> Javier Martinez Canillas <javier@osg.samsung.com> writes:
>>
>>> Thanks for reporting this issue. I only did a partial build with
>>> make M=drivers/bcma but didn't think about implicit dependencies
>>> on other drivers.
>>>
>>> I've posted this patch that should avoid this issue:
>>> https://patchwork.kernel.org/patch/7391551/
>>
>> So this patch ("bcma: mips: Allow build if COMPILE_TEST is enabled")
>> depend on that patch ("mtd: Make MTD_BCM47XXSFLASH to depend on MIPS"),
>> right? So I cannot apply the bcma patch until the mtd patch is in my
>> tree.
>
> That's correct, sorry for not stating it explicitly.
Ok, I put the patch now to "Awaiting Upstream" state in patchwork and
will apply it once I have the mtd patch.
--
Kalle Valo
next prev parent reply other threads:[~2015-10-14 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:41 [PATCH] bcma: mips: Allow build if COMPILE_TEST is enabled Javier Martinez Canillas
2015-10-13 15:25 ` kbuild test robot
2015-10-14 9:20 ` Javier Martinez Canillas
2015-10-14 9:42 ` [kbuild-all] " Fengguang Wu
2015-10-14 10:52 ` Kalle Valo
2015-10-14 10:54 ` Javier Martinez Canillas
2015-10-14 11:04 ` Kalle Valo [this message]
2015-10-14 11:04 ` Javier Martinez Canillas
2016-01-28 13:05 ` Kalle Valo
2016-01-28 18:58 ` Javier Martinez Canillas
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=87h9ltn23b.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=javier@osg.samsung.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=luisbg@osg.samsung.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.