Linux wireless drivers development
 help / color / mirror / Atom feed
From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	brcm80211-dev-list@cypress.com, Wright.Feng@cypress.com,
	Neil Armstrong <narmstrong@baylibre.com>,
	Christoph Muellner <christoph.muellner@theobroma-systems.com>
Subject: Re: [RESEND] brcmfmac support for BCM4359 sdio on arm64 ??
Date: Mon, 24 Jun 2019 21:04:45 +0200	[thread overview]
Message-ID: <db1e6182-d8fe-a68a-e769-b6460c68fab0@broadcom.com> (raw)
In-Reply-To: <30516339-BAD7-40F4-980B-D30CDF504A08@gmail.com>

Hi Christian,

Here it is. Hopefully unmangled this time.

Regards,
Arend
---
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c 
b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
index ec129864cc9c..7be8064c6dc7 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
@@ -785,7 +785,8 @@ void brcmf_sdiod_sgtable_alloc(struct brcmf_sdio_dev 
*sdiodev)
                       sdiodev->settings->bus.sdio.txglomsz);
         nents += (nents >> 4) + 1;

-       WARN_ON(nents > sdiodev->max_segment_count);
+       WARN(nents > sdiodev->max_segment_count, "max_seg_cnt=%u, 
host_max_seg=%u, nents=%u\n",
+                sdiodev->max_segment_count, host->max_segs, nents);

         brcmf_dbg(TRACE, "nents=%d\n", nents);
         err = sg_alloc_table(&sdiodev->sgtable, nents, GFP_KERNEL);

  reply	other threads:[~2019-06-24 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08  3:39 [RESEND] brcmfmac support for BCM4359 sdio on arm64 ?? Christian Hewitt
2019-06-11  9:45 ` Arend Van Spriel
2019-06-12  8:22   ` Christian Hewitt
2019-06-24 15:45   ` Christian Hewitt
2019-06-24 19:04     ` Arend Van Spriel [this message]
2019-06-30 17:06       ` Christian Hewitt
2019-11-21  3:52       ` Christian Hewitt
2019-11-21  9:00         ` Arend Van Spriel
2019-11-21 12:01           ` Christian Hewitt
     [not found]             ` <096CB8E8-5D24-4EEF-B283-746D6AA7C105@gmail.com>
2019-12-12  9:07               ` Arend Van Spriel

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=db1e6182-d8fe-a68a-e769-b6460c68fab0@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=Wright.Feng@cypress.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211-dev-list@cypress.com \
    --cc=christianshewitt@gmail.com \
    --cc=christoph.muellner@theobroma-systems.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=narmstrong@baylibre.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