> Having a quiet deprecation warning with the understanding that things
> will stay around for *years* is fine. Although it makes me wonder how
> much value the deprecation message really adds. I mean, why the hell
> print a message, when the only correct thing to do is to just look at
> and fix Xo
On 16 December 2014 at 11:03, Linus Torvalds
wrote:
> On Mon, Dec 15, 2014 at 4:48 PM, Dave Airlie wrote:
>>
>> I'd be inclined to just revert this for now, it is annoying we let
>> userspace away with this, but we probably need to find a better
>> way to enforce it, since the cat is out of the b
On 16 December 2014 at 10:35, Linus Torvalds
wrote:
> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
>>
>> i915:
>> Initial Skylake (SKL) support
>> gen3/4 reset work
>> start of dri1/ums removal
>> infoframe tracking
>> fixes for lots of things.
>
>
On Mon, Dec 15, 2014 at 04:35:29PM -0800, Linus Torvalds wrote:
> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
> >
> > i915:
> > Initial Skylake (SKL) support
> > gen3/4 reset work
> > start of dri1/ums removal
> > infoframe tracking
> > fixes for lo
On Tue, Dec 16, 2014 at 12:37:52PM +1000, Dave Airlie wrote:
> > Having a quiet deprecation warning with the understanding that things
> > will stay around for *years* is fine. Although it makes me wonder how
> > much value the deprecation message really adds. I mean, why the hell
> > print a messa
On 12/16/2014 07:18 AM, Thomas Hellstrom wrote:
> On 12/16/2014 01:35 AM, Linus Torvalds wrote:
>> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
>>> i915:
>>> Initial Skylake (SKL) support
>>> gen3/4 reset work
>>> start of dri1/ums removal
>>> infoframe trac
On 12/16/2014 01:35 AM, Linus Torvalds wrote:
> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
>> i915:
>> Initial Skylake (SKL) support
>> gen3/4 reset work
>> start of dri1/ums removal
>> infoframe tracking
>> fixes for lots of things.
> So I'm not s
On Mon, Dec 15, 2014 at 7:48 PM, Dave Airlie wrote:
> On 16 December 2014 at 10:35, Linus Torvalds
> wrote:
>> On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
>>>
>>> i915:
>>> Initial Skylake (SKL) support
>>> gen3/4 reset work
>>> start of dri1/ums removal
>>>
On Mon, Dec 15, 2014 at 6:37 PM, Dave Airlie wrote:
>
> Now I've no idea if this happens with SNA it probably does, but it it
> didn't then F20 is using UXA so hardly anyone at Intel would see it.
Ugh, ok. I haven't upgraded to F21 yet, and won't until the merge
window is over and my life is back
On Mon, Dec 15, 2014 at 5:50 PM, Dave Airlie wrote:
>
> Now you might complain that printing anything in this case is bad,
I don't mind it if it's *one* line, and if people realize that the
commentary in the commit in question was pure and utter shit.
Because talking about how it's going to beco
On Mon, Dec 15, 2014 at 4:48 PM, Dave Airlie wrote:
>
> I'd be inclined to just revert this for now, it is annoying we let
> userspace away with this, but we probably need to find a better
> way to enforce it, since the cat is out of the bag.
.. why did that commit ever even get far enough to get
On Sun, Dec 14, 2014 at 11:17 PM, Dave Airlie wrote:
>
> i915:
> Initial Skylake (SKL) support
> gen3/4 reset work
> start of dri1/ums removal
> infoframe tracking
> fixes for lots of things.
So I'm not sure how happy I am about this. It seems to work, but
Hi Linus,
This is the main drm pull, as explained this was queued behind arm soc and
iommu, the diffstat seems confused which worries me always, but I've git pull'ed
this tree into yours and gotten a minor conflict in mm/hugetlb.c, which is
easily solved. The -mm changes from the AMD HSA driver
13 matches
Mail list logo
