ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mitchell Nordine <mitchell.nordine@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: Fwd: XPS 9310 MSI vectors patch for ath11k
Date: Mon, 16 Nov 2020 11:30:15 +0200	[thread overview]
Message-ID: <87ima51wew.fsf@codeaurora.org> (raw)
In-Reply-To: <CAJxb_ErL6NhWNxp_yxFmTqB9v1q3VL399+V+yL4n3L1aBWuocQ@mail.gmail.com> (Mitchell Nordine's message of "Sun, 15 Nov 2020 23:12:41 +0100")

(adding back ath11k list, please don't drop it so that others can also
see and participate the discussion)

Mitchell Nordine <mitchell.nordine@gmail.com> writes:

>> To pinpoint the problem can you try Carl's suggestion adding
>> "memmap=12M\$20M" to kernel parameters:
>>
>> http://lists.infradead.org/pipermail/ath11k/2020-November/000686.html
>>
>> Let me know how it goes.
>
> Thanks for the suggestion. I have given this a go but haven't noticed
> any change in behaviour.

Ok, thanks for testing.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

      parent reply	other threads:[~2020-11-16  9:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJxb_EpOy-CqJhodHMcBDuOgeQoZrtims9stB4uGxz7kCz_Y7Q@mail.gmail.com>
     [not found] ` <877dqn3m3t.fsf@codeaurora.org>
     [not found]   ` <CAJxb_EoTvUV3Bwq4O7DMS1AgvWD3VLq9e5Z_Y8FeGbSFxmvzbg@mail.gmail.com>
2020-11-15 15:16     ` Fwd: XPS 9310 MSI vectors patch for ath11k Mitchell Nordine
2020-11-15 19:35       ` Kalle Valo
     [not found]         ` <CAJxb_ErL6NhWNxp_yxFmTqB9v1q3VL399+V+yL4n3L1aBWuocQ@mail.gmail.com>
2020-11-16  9:30           ` Kalle Valo [this message]

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=87ima51wew.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mitchell.nordine@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