From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Olof Johansson <olof.johansson@gmail.com>,
wufan@codeaurora.org, Arnd Bergmann <arnd@arndb.de>,
Jeffrey Hugo <jhugo@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
pratanan@codeaurora.org, LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Jason Gunthorpe <jgg@mellanox.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [RFC PATCH 0/8] Qualcomm Cloud AI 100 driver
Date: Wed, 20 May 2020 07:54:38 +0200 [thread overview]
Message-ID: <20200520055438.GA2236242@kroah.com> (raw)
In-Reply-To: <20200520051135.GA11847@yoga>
On Tue, May 19, 2020 at 10:11:35PM -0700, Bjorn Andersson wrote:
> On Tue 19 May 21:59 PDT 2020, Greg Kroah-Hartman wrote:
>
> > On Tue, May 19, 2020 at 10:41:15PM +0200, Daniel Vetter wrote:
> > > > Ok, that's a decision you are going to have to push upward on, as we
> > > > really can't take this without a working, open, userspace.
> > >
> > > Uh wut.
> > >
> > > So the merge criteria for drivers/accel (atm still drivers/misc but I
> > > thought that was interim until more drivers showed up) isn't actually
> > > "totally-not-a-gpu accel driver without open source userspace".
> > >
> > > Instead it's "totally-not-a-gpu accel driver without open source
> > > userspace" _and_ you have to be best buddies with Greg. Or at least
> > > not be on the naughty company list. Since for habanalabs all you
> > > wanted is a few test cases to exercise the ioctls. Not the entire
> > > userspace.
> >
> > Habanalabs now has their full library opensourced that their tools use
> > directly, so that's not an argument anymore.
> >
> > My primary point here is the copyright owner of this code, because of
> > that, I'm not going to objet to allowing this to be merged without open
> > userspace code.
> >
>
> So because it's copyright Linux Foundation you are going to accept it
> without user space, after all?
Huh, no, the exact opposite, sorry, drop the "not" in that above
sentence. My bad.
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-20 5:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:41 [RFC PATCH 0/8] Qualcomm Cloud AI 100 driver Daniel Vetter
2020-05-19 23:26 ` Jason Gunthorpe
2020-05-20 4:59 ` Greg Kroah-Hartman
2020-05-20 5:11 ` Bjorn Andersson
2020-05-20 5:54 ` Greg Kroah-Hartman [this message]
2020-05-20 5:15 ` Greg Kroah-Hartman
2020-05-20 8:34 ` Daniel Vetter
2020-05-20 14:48 ` Jeffrey Hugo
2020-05-20 15:56 ` Daniel Vetter
2020-05-20 15:59 ` Greg Kroah-Hartman
2020-05-20 16:15 ` Jeffrey Hugo
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=20200520055438.GA2236242@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@mellanox.com \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=olof.johansson@gmail.com \
--cc=pratanan@codeaurora.org \
--cc=wufan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).