From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: ath11k@lists.infradead.org, jk@ozlabs.org
Subject: Re: patchwork
Date: Tue, 23 Apr 2019 17:44:45 +0300 [thread overview]
Message-ID: <87sgu8ye5e.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <bd15fd3e-a0fb-02b1-05d8-8df1bb3902a2@phrozen.org> (John Crispin's message of "Wed, 17 Apr 2019 12:17:17 +0200")
John Crispin <john@phrozen.org> writes:
> could you kindly setup a patchwork for the ath11k list ?
I already requested kernel.org admins to setup one but I have not heard
back yet.
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-04-23 14:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 10:17 patchwork John Crispin
2019-04-23 14:44 ` Kalle Valo [this message]
2019-04-23 14:49 ` patchwork Jeremy Kerr
2019-04-23 15:06 ` patchwork Kalle Valo
2019-05-06 12:53 ` patchwork Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2022-03-15 20:55 Patchwork Ryan Eatmon
2022-03-15 20:55 Patchwork Ryan Eatmon
2019-05-03 17:18 patchwork akuster808
2019-05-12 18:04 ` patchwork akuster808
2019-05-13 7:27 ` patchwork Zoran Stojsavljevic
2019-05-13 7:32 ` patchwork Mark Hatle
2011-12-07 11:35 Patchwork Ralf Baechle
2010-04-09 5:46 Initial work on an Android SDK via openembedded Angus Lees
2010-04-10 13:01 ` GNUtoo
2010-04-15 17:56 ` Patchwork Konrad Mattheis
2010-04-15 18:59 ` Patchwork Philip Balister
2009-11-11 14:55 Patchwork Ralf Baechle
2009-11-06 15:37 patchwork Chris Mason
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=87sgu8ye5e.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=jk@ozlabs.org \
--cc=john@phrozen.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.