From: Kalle Valo <kvalo@codeaurora.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: Brian Norris <briannorris@chromium.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>,
ath10k <ath10k@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Rakesh Pillai <pillair@codeaurora.org>
Subject: Re: [PATCH] ath10k: add option for chip-id based BDF selection
Date: Tue, 10 Nov 2020 19:33:46 +0200 [thread overview]
Message-ID: <87imadce11.fsf@codeaurora.org> (raw)
In-Reply-To: <CACTWRwtjvQYUvbWHrajNRkK_sDZRv1hr0kp+o1=6504qv64qKQ@mail.gmail.com> (Abhishek Kumar's message of "Tue, 10 Nov 2020 09:19:20 -0800")
Abhishek Kumar <kuabhs@chromium.org> writes:
> Apologies for the delay, was busy so could not work on V2 . I have
> started working on V2 patch. Will upload by today/tomorrow.
Thanks, I'll then drop this v1.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Abhishek Kumar <kuabhs@chromium.org>
Cc: Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Rakesh Pillai <pillair@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: add option for chip-id based BDF selection
Date: Tue, 10 Nov 2020 19:33:46 +0200 [thread overview]
Message-ID: <87imadce11.fsf@codeaurora.org> (raw)
In-Reply-To: <CACTWRwtjvQYUvbWHrajNRkK_sDZRv1hr0kp+o1=6504qv64qKQ@mail.gmail.com> (Abhishek Kumar's message of "Tue, 10 Nov 2020 09:19:20 -0800")
Abhishek Kumar <kuabhs@chromium.org> writes:
> Apologies for the delay, was busy so could not work on V2 . I have
> started working on V2 patch. Will upload by today/tomorrow.
Thanks, I'll then drop this v1.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-10 17:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 0:51 [PATCH] ath10k: add option for chip-id based BDF selection Abhishek Kumar
2020-10-20 0:51 ` Abhishek Kumar
2020-10-20 15:35 ` Doug Anderson
2020-10-20 15:35 ` Doug Anderson
2020-10-23 21:13 ` Abhishek Kumar
2020-10-23 21:13 ` Abhishek Kumar
[not found] ` <CACTWRwtqcMxZKhDR-Q+3CyOw0Ju=iR+ZMg2pVrHEuzbOUebjOg@mail.gmail.com>
[not found] ` <001a01d6aa24$6ceaf390$46c0dab0$@codeaurora.org>
2020-10-26 22:51 ` Doug Anderson
2020-10-26 22:51 ` Doug Anderson
2020-10-27 5:17 ` Rakesh Pillai
2020-10-27 5:17 ` Rakesh Pillai
2020-10-27 14:56 ` Doug Anderson
2020-10-27 14:56 ` Doug Anderson
2020-10-27 15:11 ` Rakesh Pillai
2020-10-27 15:11 ` Rakesh Pillai
2020-11-06 7:11 ` Kalle Valo
2020-11-06 7:11 ` Kalle Valo
2020-11-10 17:19 ` Abhishek Kumar
2020-11-10 17:19 ` Abhishek Kumar
2020-11-10 17:33 ` Kalle Valo [this message]
2020-11-10 17:33 ` 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=87imadce11.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=kuabhs@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pillair@codeaurora.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.