dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Roland Scheidegger <rscheidegger.oss@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
	Linux-graphics-maintainer <linux-graphics-maintainer@vmware.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] feature/staging_sm5
Date: Tue, 24 Mar 2020 00:47:02 +0100	[thread overview]
Message-ID: <1a637628-c787-537e-7a68-76e5b45c48d7@gmail.com> (raw)
In-Reply-To: <59050049-7fb4-b3c1-c9f3-df1bf26d2e4e@gmail.com>

Am 23.03.20 um 19:43 schrieb Roland Scheidegger:
> Am 23.03.20 um 01:36 schrieb Dave Airlie:
>> On Sat, 21 Mar 2020 at 08:57, Roland Scheidegger (VMware)
>> <rscheidegger.oss@gmail.com> wrote:
>>>
>>> Dave, Daniel,
>>>
>>> vmwgfx pull for for 5.7. Needed for GL4 functionality.
>>> Sync up device headers, add support for new commands, code
>>> refactoring around surface definition.
>>
>> Two things,
>>
>> 1.for some reason patchwork didn't process this, Daniel might be able
>> to tell me why I forget who to ask everytime :-)
>>
>> 2. Not sure how happy fd.o gitlab is to host kernel trees, might be
>> safe to stick to old school anongit until we work it out.
> Alright I put it up here now (after fiddling with it for a long time I
> figured out how to do it...):
> https://cgit.freedesktop.org/~sroland/linux/

Ok I'm sending out a new pull request.
I've sent out a second version, with fixed r-b and s-o-b email addresses.
Patchwork now seems to have picked it up (even the first series?).

Roland


> 
> 
>>
>> I'm happy to process this but it should be in patchwork so we can make
>> sure the process is followed.
> Ok I guess I did something wrong but I really need to know what :-).
> Sorry I'm new to this workflow.
> 
> Roland
> 
>>
>> Dave.
>>>
>>> Preliminary mesa userspace code using these new vmwgfx features
>>> can be found at: https://gitlab.freedesktop.org/bhenden/mesa
>>>
>>> The following changes since commit dad569af718c4e603c35f59ed03bf0555633dd95:
>>>
>>>   drm/vmwgfx: Refuse DMA operation when SEV encryption is active (2020-01-28 09:27:45 +0100)
>>>
>>> are available in the Git repository at:
>>>
>>>   git@gitlab.freedesktop.org:sroland/vmwgfx_drm.git feature/staging_sm5
>>>
>>> for you to fetch changes up to 4526035058cc6cc09afbca3a5d86862438ae1edf:
>>>
>>>   drm/vmwgfx: Use vmwgfx version 2.18 to signal SM5 compatibility (2020-03-20 23:35:53 +0100)
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-03-23 23:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 22:56 [git pull] feature/staging_sm5 Roland Scheidegger (VMware)
2020-03-23  0:36 ` Dave Airlie
2020-03-23 18:43   ` Roland Scheidegger
2020-03-23 23:47     ` Roland Scheidegger [this message]
2020-03-23 23:54 Roland Scheidegger (VMware)

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=1a637628-c787-537e-7a68-76e5b45c48d7@gmail.com \
    --to=rscheidegger.oss@gmail.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-graphics-maintainer@vmware.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;
as well as URLs for NNTP newsgroup(s).