From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org,
DRI <dri-devel@lists.freedesktop.org>,
linux-next@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the drm-intel-fixes tree
Date: Tue, 03 Jan 2017 15:25:24 +0200 [thread overview]
Message-ID: <8737h0i8cb.fsf@intel.com> (raw)
In-Reply-To: <20170103092317.slzmtrdzzrjzbypw@zhen-hp.sh.intel.com>
On Tue, 03 Jan 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2017.01.02 21:48:57 -0700, Alex Williamson wrote:
>> > Alex, I liked to have kvmgt related mdev interface change be merged through
>> > vfio tree, but wasn't awared one of Jike's fix had conflict. Could you apply
>> > below fix in your tree? I think in general for possible interface change in
>> > future we still need a pull request for i915 to resolve dependence earlier.
>>
>> Hi Zhenyu,
>>
>> Hopefully this abstraction will help to isolate vendor drivers from
>> mdev API changes in the future. I can certainly roll this patch into
>> the original to maintain bisectability. I want to get these changes in
>> for rc3, will a pull request for the i915 changes be sent this week?
>
> Send to Jani who is managing i915 fixes pull.
Send what to me? I've pushed fixes to drm-intel-fixes today for testing,
and expect to send a pull request to Dave early Thursday. If there's a
conflict, it can usually be solved while merging, like Stephen has done.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
linux-kernel@vger.kernel.org,
DRI <dri-devel@lists.freedesktop.org>,
linux-next@vger.kernel.org
Subject: Re: [Intel-gfx] linux-next: build failure after merge of the drm-intel-fixes tree
Date: Tue, 03 Jan 2017 15:25:24 +0200 [thread overview]
Message-ID: <8737h0i8cb.fsf@intel.com> (raw)
In-Reply-To: <20170103092317.slzmtrdzzrjzbypw@zhen-hp.sh.intel.com>
On Tue, 03 Jan 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2017.01.02 21:48:57 -0700, Alex Williamson wrote:
>> > Alex, I liked to have kvmgt related mdev interface change be merged through
>> > vfio tree, but wasn't awared one of Jike's fix had conflict. Could you apply
>> > below fix in your tree? I think in general for possible interface change in
>> > future we still need a pull request for i915 to resolve dependence earlier.
>>
>> Hi Zhenyu,
>>
>> Hopefully this abstraction will help to isolate vendor drivers from
>> mdev API changes in the future. I can certainly roll this patch into
>> the original to maintain bisectability. I want to get these changes in
>> for rc3, will a pull request for the i915 changes be sent this week?
>
> Send to Jani who is managing i915 fixes pull.
Send what to me? I've pushed fixes to drm-intel-fixes today for testing,
and expect to send a pull request to Dave early Thursday. If there's a
conflict, it can usually be solved while merging, like Stephen has done.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-01-03 13:25 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 23:42 linux-next: build failure after merge of the drm-intel-fixes tree Stephen Rothwell
2017-01-02 23:42 ` Stephen Rothwell
2017-01-03 2:59 ` Zhenyu Wang
2017-01-03 2:59 ` Zhenyu Wang
2017-01-03 4:07 ` Stephen Rothwell
2017-01-03 4:07 ` Stephen Rothwell
2017-01-03 4:48 ` Alex Williamson
2017-01-03 4:48 ` Alex Williamson
2017-01-03 9:23 ` Zhenyu Wang
2017-01-03 9:23 ` Zhenyu Wang
2017-01-03 13:25 ` Jani Nikula [this message]
2017-01-03 13:25 ` [Intel-gfx] " Jani Nikula
2017-01-03 20:37 ` Alex Williamson
2017-01-03 20:37 ` [Intel-gfx] " Alex Williamson
2017-01-04 9:07 ` Daniel Vetter
2017-01-04 9:07 ` [Intel-gfx] " Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2022-07-13 12:14 Stephen Rothwell
2022-07-13 12:14 ` Stephen Rothwell
2022-01-31 22:27 Stephen Rothwell
2022-01-31 22:27 ` Stephen Rothwell
2020-11-03 22:37 Stephen Rothwell
2020-11-03 22:37 ` Stephen Rothwell
2020-11-04 0:25 ` Rodrigo Vivi
2020-11-04 0:25 ` Rodrigo Vivi
2020-06-15 23:39 Stephen Rothwell
2020-06-15 23:39 ` Stephen Rothwell
2020-06-16 9:22 ` Joonas Lahtinen
2020-06-16 9:22 ` Joonas Lahtinen
2020-05-28 22:30 Stephen Rothwell
2020-05-28 22:30 ` Stephen Rothwell
2020-01-20 21:34 Stephen Rothwell
2020-01-20 21:34 ` Stephen Rothwell
2020-01-21 7:13 ` Joonas Lahtinen
2020-01-21 7:13 ` Joonas Lahtinen
2019-01-29 22:39 Stephen Rothwell
2019-01-29 22:53 ` Lucas De Marchi
2019-01-30 8:22 ` Jani Nikula
2018-05-29 9:26 Stephen Rothwell
2018-05-29 9:26 ` Stephen Rothwell
2018-05-29 11:45 ` Joonas Lahtinen
2018-05-29 11:45 ` Joonas Lahtinen
2017-10-10 7:03 Mark Brown
2017-10-11 8:51 ` Mark Brown
2017-10-11 8:51 ` Mark Brown
2014-06-06 2:03 Stephen Rothwell
2014-06-06 2:03 ` Stephen Rothwell
2014-06-06 6:45 ` Daniel Vetter
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=8737h0i8cb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=alex.williamson@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zhenyuw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.