linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Necip Fazil Yildiran <fazilyildiran@gmail.com>, hauke@hauke-m.de
Cc: szajec5@gmail.com, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org, paul@pgazz.com, jeho@cs.utexas.edu
Subject: Re: [PATCH] MIPS: BMC47xx: fix kconfig dependency bug for BCM47XX_SSB
Date: Fri, 6 Nov 2020 11:24:41 +0300	[thread overview]
Message-ID: <547e42cd-f39b-1128-4836-82891dd770d1@gmail.com> (raw)
In-Reply-To: <20201104164126.36399-1-fazilyildiran@gmail.com>

Hello!

On 04.11.2020 19:41, Necip Fazil Yildiran wrote:

> When BCM47XX_SSB is enabled and SSB_PCIHOST is disabled, it results in the
> following Kbuild warning:
> 
> WARNING: unmet direct dependencies detected for SSB_B43_PCI_BRIDGE
>    Depends on [n]: SSB [=y] && SSB_PCIHOST [=n]
>    Selected by [y]:
>    - BCM47XX_SSB [=y] && BCM47XX [=y] && PCI [=y]
> 
> The reason is that BCM47XX_SSB selects SSB_B43_PCI_BRIDGE without
> depending on or selecting SSB_PCIHOST while SSB_B43_PCI_BRIDGE depends on
> SSB_PCIHOST. This can also fail building the kernel as demonstrated in a
> bug report.
> 
> Honor the kconfig dependency to remove unmet direct dependency warnings
> and avoid any potential build failures.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=210051

    Isn't that tag supposed to be used for the patch mail itself? At least
that's what I'm seeing in the USB patches where it points to the msg with
a patch...

> Signed-off-by: Necip Fazil Yildiran <fazilyildiran@gmail.com>
[...]

MBR, Sergei

  reply	other threads:[~2020-11-06  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 16:41 [PATCH] MIPS: BMC47xx: fix kconfig dependency bug for BCM47XX_SSB Necip Fazil Yildiran
2020-11-06  8:24 ` Sergei Shtylyov [this message]
2020-11-12 22:38 ` Thomas Bogendoerfer

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=547e42cd-f39b-1128-4836-82891dd770d1@gmail.com \
    --to=sergei.shtylyov@gmail.com \
    --cc=fazilyildiran@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=jeho@cs.utexas.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@pgazz.com \
    --cc=szajec5@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;
as well as URLs for NNTP newsgroup(s).