stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Jani Nikula <jani.nikula@intel.com>,
	stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Include asm sources for {ivb, hsw}_clear_kernel.c
Date: Tue, 09 Jun 2020 19:18:06 -0300	[thread overview]
Message-ID: <ortuzjx4rl.fsf@livre.home> (raw)
In-Reply-To: <159163988890.30073.8976615673203599761@build.alporthouse.com> (Chris Wilson's message of "Mon, 08 Jun 2020 19:11:28 +0100")

On Jun  8, 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:

> Quoting Rodrigo Vivi (2020-06-08 18:46:53)
>> Alexandre Oliva has recently removed these files from Linux Libre
>> with concerns that the sources weren't available.
>> 
>> The sources are available on IGT repository, and only open source
>> tools are used to generate the {ivb,hsw}_clear_kernel.c files.
>> 
>> However, the remaining concern from Alexandre Oliva was around
>> GPL license and the source not been present when distributing
>> the code.

Thanks for looking into this, and for addressing the potential issues so
promptly.

>> let's make sure that we do include the asm sources here in our tree.

+1  having sources handy is good!

>> Btw, I tried to have some diligence here and make sure that the
>> asms that these commits are adding are truly the source for
>> the mentioned files:

Excellent!

> Should there not be instructions on how to generate the object code?

Considering that a script is used to generate it, to the point of adding
some of the comments in the output, it might be a good idea to include
it too, especially considering that scripts that control compilation are
part of the complete corresponding source code under the GNU GPL.


IMHO, a link to help users locate the assembler, as comments in the
script, would be welcome, though not mandatory IIUC.  Even though such
links tend to rot over time, they at least offer encouragement to start
or carry on a search ;-)


Thanks again,

-- 
Alexandre Oliva, freedom fighter    he/him    https://FSFLA.org/blogs/lxo/
Free Software Evangelist              Stallman was right, but he's left :(
GNU Toolchain Engineer           Live long and free, and prosper ethically

  reply	other threads:[~2020-06-09 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 17:46 [PATCH] drm/i915: Include asm sources for {ivb,hsw}_clear_kernel.c Rodrigo Vivi
2020-06-08 18:11 ` [Intel-gfx] [PATCH] drm/i915: Include asm sources for {ivb, hsw}_clear_kernel.c Chris Wilson
2020-06-09 22:18   ` Alexandre Oliva [this message]
2020-06-10 20:18   ` [PATCH] drm/i915: Include asm sources for {ivb,hsw}_clear_kernel.c Rodrigo Vivi
2020-06-12 21:15     ` [Intel-gfx] [PATCH] drm/i915: Include asm sources for {ivb, hsw}_clear_kernel.c Bloomfield, Jon
2020-06-15 18:54       ` Rodrigo Vivi

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=ortuzjx4rl.fsf@livre.home \
    --to=lxoliva@fsfla.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).