On 4/20/22 7:08 AM, Christoph Hellwig wrote:
> On Thu, Apr 14, 2022 at 11:38:59AM -0300, Jason Gunthorpe wrote:
>> pull requests can flow through more than one tree concurrently. The
>> purpose of the topic branch is to allow all the commits to be in all
>> the trees they need to be in at once.
>>
On Thu, Apr 14, 2022 at 02:25:36PM +, Wang, Zhi A wrote:
> > So drop the '[DONT PULL]' commit and send a PR to the next DRM tree -
> > when that is confirmed send the same PR to vfio,
>
> I updated the branch again, but I am confused. What is the purpose of sending
> the PR to next DRM tree?
On 4/14/22 1:43 PM, Jason Gunthorpe wrote:
> On Thu, Apr 14, 2022 at 04:40:11PM +0300, Jani Nikula wrote:
>
>> git clone https://github.com/intel/gvt-linux -b for-christoph
>
> There are alot of extra commits on there - is it possible to base this
> straight on rc1 not on some kind
On Thu, 14 Apr 2022, Jason Gunthorpe wrote:
> On Thu, Apr 14, 2022 at 01:39:11PM +, Wang, Zhi A wrote:
>> This one belongs to i915, which has already been queued in drm-intel-next,
>> but
>> not yet reached to the top. When it is landed in -rc, I will rebase this
>> branch
>> on it, then we
On Thu, Apr 14, 2022 at 04:40:11PM +0300, Jani Nikula wrote:
> >> >> git clone https://github.com/intel/gvt-linux -b for-christoph
> >> >
> >> > There are alot of extra commits on there - is it possible to base this
> >> > straight on rc1 not on some kind of existing DRM tree?
> >> >
> >> > Why
On Thu, Apr 14, 2022 at 01:39:11PM +, Wang, Zhi A wrote:
> On 4/14/22 1:34 PM, Jason Gunthorpe wrote:
> > On Thu, Apr 14, 2022 at 12:20:42PM +, Wang, Zhi A wrote:
> >> On 4/13/22 11:20 PM, Jason Gunthorpe wrote:
> >>> On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
> Hi fo
On Thu, 14 Apr 2022, Jason Gunthorpe wrote:
> On Thu, Apr 14, 2022 at 12:20:42PM +, Wang, Zhi A wrote:
>> On 4/13/22 11:20 PM, Jason Gunthorpe wrote:
>> > On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
>> >> Hi folks:
>> >>
>> >> Thanks so much for the efforts. I prepared a branc
On 4/14/22 1:34 PM, Jason Gunthorpe wrote:
> On Thu, Apr 14, 2022 at 12:20:42PM +, Wang, Zhi A wrote:
>> On 4/13/22 11:20 PM, Jason Gunthorpe wrote:
>>> On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
Hi folks:
Thanks so much for the efforts. I prepared a branch whic
On Thu, Apr 14, 2022 at 12:20:42PM +, Wang, Zhi A wrote:
> On 4/13/22 11:20 PM, Jason Gunthorpe wrote:
> > On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
> >> Hi folks:
> >>
> >> Thanks so much for the efforts. I prepared a branch which contains all our
> >> patches.The aim of th
On 4/13/22 11:20 PM, Jason Gunthorpe wrote:
> On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
>> Hi folks:
>>
>> Thanks so much for the efforts. I prepared a branch which contains all our
>> patches.The aim of the branch is for the VFIO maintainers to pull the whole
>> bunch easily a
On Wed, Apr 13, 2022 at 11:13:06PM +, Wang, Zhi A wrote:
> Hi folks:
>
> Thanks so much for the efforts. I prepared a branch which contains all our
> patches.The aim of the branch is for the VFIO maintainers to pull the whole
> bunch easily after the drm-intel-next got merged through drm (as
Hi folks:
Thanks so much for the efforts. I prepared a branch which contains all our
patches.The aim of the branch is for the VFIO maintainers to pull the whole
bunch easily after the drm-intel-next got merged through drm (as one of the
MMIO patches depends on a patch in drm-intel-next).
I dro
On Wed, 13 Apr 2022, Christoph Hellwig wrote:
> On Wed, Apr 13, 2022 at 01:47:05PM +, Wang, Zhi A wrote:
>> > the GVT code in the i915 is a bit of a mess right now due to strange
>> > abstractions and lots of indirect calls. This series refactors various
>> > bits to clean that up. The main
On 4/11/22 2:13 PM, Christoph Hellwig wrote:
> Hi all,
>
> the GVT code in the i915 is a bit of a mess right now due to strange
> abstractions and lots of indirect calls. This series refactors various
> bits to clean that up. The main user visible change is that almost all
> of the GVT code move
14 matches
Mail list logo