All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	"Hante Meuleman" <meuleman@broadcom.com>,
	"brcm80211 development" <brcm80211-dev-list@broadcom.com>
Subject: Re: [PATCH] brcmfmac: use direct data pointer in NVRAM parser struct
Date: Thu, 4 Jun 2015 16:55:31 +0200	[thread overview]
Message-ID: <557066E3.6030008@broadcom.com> (raw)
In-Reply-To: <87y4jzpn6x.fsf@kamboji.qca.qualcomm.com>

On 06/04/15 16:23, Kalle Valo wrote:
> Hi Arend,
>
> Arend van Spriel<arend@broadcom.com>  writes:
>
>>>> I really don't want to have you annoyed because the need of rebasing
>>>> your patch. What you said about Ralf's tree and linux-next isn't
>>>> exactly true. I do believe Kalle won't merge linux-next into
>>>> wireless-driver-next, so we have to wait for 4.2-rc1, then for Dave
>>>> merging Linus's tree, then Kalle merging Dave's tree.
>>>
>>> Well, it is an integration issue. So yes, wireless-drivers-next (and
>>> net-next) would not build for CONFIG_BCM47XX with the brcmfmac patch,
>>> because of the missing mips patch. However, the linux-next tree will
>>> have no build issue and consequently 4.2-rc1 will have no build issue. I
>>> think this is acceptable although I would like to hear the opinion of
>>> Kalle on this.
>>
>> Hi Kalle,
>>
>> Do you have an opinion on this? mips-next and linux-next now have the
>> function brcmfmac needs for CONFIG_BCM47XX so I could submit brcmfmac
>> patch, but that means wireless-drivers-next (and net-next) will not
>> build for CONFIG_BCM47XX until after the 4.2 merge window.
>
> The answer is clear: we must not ever break the build deliberately, in
> under any circumstances. Mistakes of course always happen but if we know
> a patch will break the build it should not be applied.
>
> So if patch A has a build dependency on patch B in another tree, we have
> to wait for that patch B to trickle down to wireless-drivers-next before
> I can commit patch A. There are other ways to speed this up if really
> needed but I don't see this case is important enough for the extra
> hurdle.
>
> I haven't followed all the details so I might be missing something but I
> think it would be good just to wait for 4.2-rc1, it's not that far
> anyway, and go with the original Arend's plan.

Ok. I will submit the brcmfmac patch relying on the mips change to 
wireless-drivers-next for 4.3 after 4.2-rc1 merge window. I will ack the 
patch from Rafal in seperate email.

Regards,
Arend

  reply	other threads:[~2015-06-04 14:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 11:37 [PATCH] brcmfmac: use direct data pointer in NVRAM parser struct Rafał Miłecki
2015-05-28 11:54 ` Arend van Spriel
2015-05-28 12:34   ` Rafał Miłecki
2015-05-28 21:24     ` Arend van Spriel
2015-05-29  5:20       ` Rafał Miłecki
2015-05-29  8:03         ` Arend van Spriel
2015-05-29 15:58           ` Rafał Miłecki
2015-06-03 12:12           ` Arend van Spriel
2015-06-04 14:23             ` Kalle Valo
2015-06-04 14:55               ` Arend van Spriel [this message]
2015-06-04 15:02 ` Arend van Spriel
2015-06-04 19:59   ` Rafał Miłecki
2015-06-04 20:11 ` [PATCH RESEND] " Rafał Miłecki
2015-06-08 11:31   ` 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=557066E3.6030008@broadcom.com \
    --to=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=meuleman@broadcom.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.