[PATCH 0/2] Expose the DRM version

Andy Whitcroft apw at canonical.com
Mon Mar 15 12:49:07 GMT 2010


On Mon, Mar 15, 2010 at 02:29:06PM +0200, Amit Kucheria wrote:
> On 10 Mar 15, Andy Whitcroft wrote:
> > Now that we have a major backport of DRM in the kernel we want to be able
> > to clearly identify the version carried programatically.  In particular
> > we want this information available in the boot dmesg and in the apport
> > data collected.
> > 
> > The following patches augment the /proc/version_signature to expose the
> > full official build version number in the Makefile.  The value in this
> > file is already emitted during early boot into dmesg.  This allows
> > the -rcN release candidate number or stable release version to be exposed
> > in the default case.  By manually augmenting the EXTRAVERSION with our
> > DRM backport information we also can expose that as required.
> > 
> > In this case we set the EXTRAVERSION to '.9+drm33.0' indicating that we
> > have 2.6.32.9 stable update applied plus the drm33 at the release version.
> > The .0 will increment to match 2.6.33.y stable updates as they are applied.
> > 
> > -apw
> > 
> > Andy Whitcroft (2):
> >   UBUNTU: expose the kernel EXTRAVERSION in dmesg and
> >     /proc/version_signature
> >   UBUNTU: record the drm version in EXTRAVERSION
> > 
> >  Makefile                        |    2 +-
> >  debian/rules.d/0-common-vars.mk |    3 +++
> >  debian/rules.d/2-binary-arch.mk |    2 +-
> >  3 files changed, 5 insertions(+), 2 deletions(-)
> 
> Sounds like a good idea. This will produce a conflict with each stable update
> though, correct?
> 
> Acked-by: Amit Kucheria <amit.kucheria at canonical.com>

Yes it will that, for the Linux 2.6.32.y update.  That will help to
remind us to update the drm number too.

-apw



More information about the kernel-team mailing list