From: Greg Kroah-Hartman <email@example.com> To: Dave Airlie <firstname.lastname@example.org> Cc: Jason Gunthorpe <email@example.com>, Daniel Vetter <firstname.lastname@example.org>, Linus Torvalds <email@example.com>, Oded Gabbay <firstname.lastname@example.org>, LKML <email@example.com> Subject: Re: [git pull] habanalabs pull request for kernel 5.15 Date: Fri, 20 Aug 2021 12:02:54 +0200 [thread overview] Message-ID: <YR99zh43GD3AylRY@kroah.com> (raw) In-Reply-To: <CAPM=9tyT_iouVE2v8J0SMJOLV=pr=QJOm88ud=bht4=5Ms2Y2A@mail.gmail.com> On Fri, Aug 20, 2021 at 04:48:18AM +1000, Dave Airlie wrote: > On Fri, 20 Aug 2021 at 03:07, Greg KH <firstname.lastname@example.org> wrote: > > > > On Thu, Aug 19, 2021 at 02:02:09PM +0300, Oded Gabbay wrote: > > > Hi Greg, > > > > > > This is habanalabs pull request for the merge window of kernel 5.15. > > > The commits divide roughly 50/50 between adding new features, such > > > as peer-to-peer support with DMA-BUF or signaling from within a graph, > > > and fixing various bugs, small improvements, etc. > > > > Pulled and pushed out, thanks! > > NAK for adding dma-buf or p2p support to this driver in the upstream > kernel. There needs to be a hard line between > "I-can't-believe-its-not-a-drm-driver" drivers which bypass our > userspace requirements, and I consider this the line. Damm, the first time I try to take a vacation in 1 1/2 years, and stuff like this happens :( I've now dropped this from my branch and will write more next week when I get a chance, sorry, don't have the chance to right now. thanks, greg k-h
next prev parent reply other threads:[~2021-08-20 10:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-19 11:02 Oded Gabbay 2021-08-19 17:04 ` Greg KH 2021-08-19 18:48 ` Dave Airlie 2021-08-20 6:43 ` Daniel Vetter 2021-08-20 10:02 ` Greg Kroah-Hartman [this message] 2021-08-22 23:06 ` Laurent Pinchart 2021-08-25 1:16 ` 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=YR99zh43GD3AylRY@kroah.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [git pull] habanalabs pull request for kernel 5.15' \ /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
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).