From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Cc: <jic23@kernel.org>, "Liguozhu (Kenneth)" <liguozhu@hisilicon.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
<francois.ozog@linaro.org>, <Prasad.Athreya@cavium.com>,
<arndbergmann@gmail.com>,
Alex Williamson <alex.williamson@redhat.com>,
Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
Mark Brown <broonie@kernel.org>,
<Tirumalesh.Chalamarla@cavium.com>, <jcm@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Jean-Philippe Brucker" <jean-philippe.brucker@arm.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Eric Auger <eric.auger@redhat.com>, <kvm@vger.kernel.org>,
<linux-crypto@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: Fostering linux community collaboration on hardware accelerators
Date: Mon, 16 Oct 2017 15:07:01 +0100 [thread overview]
Message-ID: <20171016150701.00004260@huawei.com> (raw)
In-Reply-To: <07d49485-e583-8434-5681-92a0b54005ca@au1.ibm.com>
<snip>
> > So as ever with a linux community focusing on a particular topic, the
> > obvious solution is a mailing list. There are a number of options on how
> > do this.
> >
> > 1) Ask one of the industry bodies to host? Who?
> >
> > 2) Put together a compelling argument for linux-accelerators@vger.kernel.org
> > as probably the most generic location for such a list.
>
> Happy to offer linux-accelerators@lists.ozlabs.org, which I can get set
> up immediately (and if we want patchwork, patchwork.ozlabs.org is
> available as always, no matter where the list is hosted).
>
That would be great! Thanks for doing this. Much easier to find out what
such a list is useful for by the practical option of having a list and
see what people do with it.
Thanks,
Jonathan
> > More open questions are
> > 1) Scope?
> > * Would anyone ever use such an overarching list?
> > * Are we better off with the usual adhoc list of 'interested parties' + lkml?
> > * Do we actually need to define the full scope - are we better with a vague
> > definition?
>
> I think a list with a broad and vaguely defined scope is a good idea -
> it would certainly be helpful to us to be able to follow what other
> contributors are doing that could be relevant to our CAPI and OpenCAPI work.
>
> >
> > 2) Is there an existing community we can use to discuss these issues?
> > (beyond the obvious firehose of LKML).
> >
> > 3) Who else to approach for input on these general questions?
> >
> > In parallel to this there are elements such as git / patchwork etc but
> > they can all be done as they are needed.
> >
> > Thanks
> >
> > --
> > Jonathan Cameron
> > Huawei
> >
>
next prev parent reply other threads:[~2017-10-16 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201710101132.v9ABUs28138304@mx0a-001b2d01.pphosted.com>
2017-10-12 5:22 ` Fostering linux community collaboration on hardware accelerators Andrew Donnellan
2017-10-12 13:31 ` Douglas Miller
2017-10-12 14:57 ` Jonathan Cameron
2017-10-12 15:48 ` Francois Ozog
2017-10-12 17:10 ` Douglas Miller
2017-10-16 14:07 ` Jonathan Cameron [this message]
2017-10-17 0:00 ` New Linux accelerators discussion list [was: Re: Fostering linux community collaboration on hardware accelerators] Andrew Donnellan
2017-10-17 12:48 ` Jonathan Cameron
2017-10-17 12:53 ` Jonathan Cameron
2017-10-10 11:28 Fostering linux community collaboration on hardware accelerators Jonathan Cameron
[not found] ` <CAHFG_=UfO54nkM68RmLmZWLtYROhaUu9U866kqTzpU=MgxfCkA@mail.gmail.com>
2017-10-11 14:43 ` Jonathan Cameron
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=20171016150701.00004260@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=Prasad.Athreya@cavium.com \
--cc=Tirumalesh.Chalamarla@cavium.com \
--cc=alex.williamson@redhat.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arndbergmann@gmail.com \
--cc=broonie@kernel.org \
--cc=eric.auger@redhat.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=francois.ozog@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jcm@redhat.com \
--cc=jean-philippe.brucker@arm.com \
--cc=jic23@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox