All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: ath11k@lists.infradead.org,
	 Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: ath11k-firmware: QCA6390 hw2.0: add RB5-specific BDF
Date: Wed, 30 Mar 2022 17:29:41 +0300	[thread overview]
Message-ID: <875ynvwm22.fsf@kernel.org> (raw)
In-Reply-To: <CAA8EJppG0FXj_n-CdGbX6b+sGrTb0_FG_tCZ0GeSEsCcz0mR3A@mail.gmail.com> (Dmitry Baryshkov's message of "Wed, 30 Mar 2022 15:57:53 +0300")

Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:

> Hi,
>
> On Fri, 18 Feb 2022 at 08:15, Dmitry Baryshkov
> <dmitry.baryshkov@linaro.org> wrote:
>> We'd like to ask for inclusion for the board file for Qualcomm Robotics
>> RB5 Development Kit.
>>
>> Following the questions from the ath10k wiki page:
>
> A gracious question. I have followed the procedure described in the
> ath10k wiki, receiving no response in the past month.

The board file updates are slow, it can take a long time before I manage
too process them.

> Is something wrong with the request?

After a quick look I didn't see anything wrong.

> We'd also like to submit several other board files:
>  - for the RB3 board (WCN3990, hw 1.0)
>  - for the Dragonboard 820c (QCA6174, hw 3.0)
>
> Do they stand a chance to be accepted?

Please do submit them.

-- 
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

  reply	other threads:[~2022-03-30 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  5:15 ath11k-firmware: QCA6390 hw2.0: add RB5-specific BDF Dmitry Baryshkov
2022-03-30 12:57 ` Dmitry Baryshkov
2022-03-30 14:29   ` Kalle Valo [this message]
2022-03-30 22:03     ` Dmitry Baryshkov
2022-04-13  8:35 ` 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=875ynvwm22.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    /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.