All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Johannes Berg <johannes.berg@intel.com>,
	 Michael Nemanov <michael.nemanov@ti.com>,
	 linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH wireless v2] wifi: wlcore: fix wlcore AP mode
Date: Mon, 17 Jun 2024 13:56:48 +0300	[thread overview]
Message-ID: <87tthrn8gf.fsf@kernel.org> (raw)
In-Reply-To: <Zm1CKAKCnuc94oIi@shell.armlinux.org.uk> (Russell King's message of "Sat, 15 Jun 2024 08:26:32 +0100")

"Russell King (Oracle)" <linux@armlinux.org.uk> writes:

> I see all my TI Wilink patches have been marked as "deferred" in the
> wireless patchwork. Please could you explain what the plan is with
> these patches, especially this one which fixes a serious frustrating
> failing that makes AP mode on this hardware very unreliable and thus
> useless.

I'm just swamped with patches, I'll try to look at these soon.

I wish that TI would take a more active role in upstream, for example
reviewing and testing patches would help a lot.

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

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

  reply	other threads:[~2024-06-17 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 19:52 [PATCH wireless v2] wifi: wlcore: fix wlcore AP mode Russell King (Oracle)
2024-06-15  7:26 ` Russell King (Oracle)
2024-06-17 10:56   ` Kalle Valo [this message]
2024-06-17 13:21     ` Russell King (Oracle)
2024-06-18  9:16       ` Kalle Valo
2024-06-18 16:50         ` Nemanov, Michael
2024-06-18  9:17 ` 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=87tthrn8gf.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=michael.nemanov@ti.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.