From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: 2 questions about git and merging
Date: Wed, 27 May 2015 07:03:48 +0200 [thread overview]
Message-ID: <55655034.1080006@ts.fujitsu.com> (raw)
In-Reply-To: <87vbffgygg.fsf@intel.com>
Am 26.05.2015 um 17:17 schrieb Jani Nikula:
> However we don't necessarily queue Skylake fixes to the current
> development kernels through drm-intel-fixes/drm-fixes, as the Skylake
> support there is anyway preliminary, the fix (I don't think we figured
> out which exact commit it was, did we?) may only end up upstream after
> the next merge window, i.e. at v4.2-rc1.
I understand you from a software developers point of view. My real world
problem is simply explained, that we do prototype testing for Skylake
now with real physical hardware. This hardware should go into prodcution
whenever Intel decides to release the Skylake platform, probably in
Q4/2015. From that date on people can buy Skylake based PCs and
workstations and they probably want to run Linux on those machines.
But they don't want to compile their own kernel, they want to stuck with
whatever is in the distributions (e.g. RHEL, SLES, Ubuntu whatever). But
also distributions have merge windows for new hardware features and the
longer it takes for a patch to show up in the vanilla tree the later it
will show up in the individual distribution kernel. Working for a
hardware vendor I see that this is bad for business. :-)
Thanks a lot for the explanations anyway, learned a lot from that.
Best regards
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE
Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany
Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@ts.fujitsu.com
Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-27 5:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 13:09 2 questions about git and merging Rainer Koenig
2015-05-26 14:04 ` Daniel Vetter
2015-05-26 15:17 ` Jani Nikula
2015-05-27 5:03 ` Rainer Koenig [this message]
2015-05-27 5:14 ` Dave Airlie
2015-05-27 6:24 ` Jani Nikula
2015-05-27 9:28 ` Daniel Vetter
2015-05-27 4:55 ` Rainer Koenig
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=55655034.1080006@ts.fujitsu.com \
--to=rainer.koenig@ts.fujitsu.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@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.