From: Kalle Valo <kvalo@codeaurora.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: ath11k@lists.infradead.org, John Crispin <john@phrozen.org>
Subject: Re: patchwork
Date: Mon, 06 May 2019 15:53:06 +0300 [thread overview]
Message-ID: <8736lrkaml.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <87lg00yd5m.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Tue, 23 Apr 2019 18:06:13 +0300")
Kalle Valo <kvalo@codeaurora.org> writes:
> Jeremy Kerr <jk@ozlabs.org> writes:
>
>> Hi John and Kalle,
>>
>>> > 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.
>>
>> I'm happy to do so for ozlabs.org, but don't want to duplicate with a
>> kernel.org setup. Let me know what you want to do here.
>
> As I already use patchwork.kernel.org with wireless-drivers patches, and
> use a custom patchwork script[1], I would prefer to use
> patchwork.kernel.org also with ath11k. For example, in case there are
> API incompatibilities etc.
>
>> If you do want to go ahead, just let me know what name you want to use
>> for the instance ("ath11k development"?), and the patchwork usernames of
>> those you want to assign as maintainers.
>
> What if we'll wait for kernel.org admins for a week or so still (I sent
> the request on April 13th, I'll ping them) and if I don't hear back,
> maybe then you could add it to ozlabs? I'll let you know how it goes.
The admins now created a project for us:
https://patchwork.kernel.org/project/ath11k/list/
--
Kalle Valo
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
prev parent reply other threads:[~2019-05-06 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 10:17 patchwork John Crispin
2019-04-23 14:44 ` patchwork Kalle Valo
2019-04-23 14:49 ` patchwork Jeremy Kerr
2019-04-23 15:06 ` patchwork Kalle Valo
2019-05-06 12:53 ` 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=8736lrkaml.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox