All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <david.weinehall@linux.intel.com>
To: tom.orourke@intel.com
Cc: intel-gfx@lists.freedesktop.org, Tom O'Rourke <Tom.O'Rourke@intel.com>
Subject: Re: [PATCH] drm/i915/guc: Use major_minor version for filename
Date: Thu, 28 Apr 2016 11:07:11 +0300	[thread overview]
Message-ID: <20160428080711.GJ18193@boom> (raw)
In-Reply-To: <1461626530-94474-1-git-send-email-tom.orourke@intel.com>

On Mon, Apr 25, 2016 at 04:22:10PM -0700, tom.orourke@intel.com wrote:
> From: Tom O'Rourke <Tom.O'Rourke@intel.com>
> 
> Load guc firmware from file with major_minor number
> in filename instead of using symolic link with only
> major number.

What's the justification for this change? Either a release
breaks ABI (or has fixes that are so important that they're
worth treating as equivalent to an ABI-break) and thus warrants
a major-number bump, or it's a minor (non-ABI-breaking) fix,
which would then fit fine within a minor number bump.

Since the firmware is released separately from the driver
this will most likely lead to more cases where the system ends up
running without any firmware loaded at all. Is that case better
than having an older revision of the same major release of the
firmware?


Kind regards, David Weinehall
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-04-28  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 23:22 [PATCH] drm/i915/guc: Use major_minor version for filename tom.orourke
2016-04-26  5:17 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-04-26 23:30   ` O'Rourke, Tom
2016-04-28  8:07 ` David Weinehall [this message]
2016-04-28  8:36   ` [PATCH] " Jani Nikula

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=20160428080711.GJ18193@boom \
    --to=david.weinehall@linux.intel.com \
    --cc=Tom.O'Rourke@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tom.orourke@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.