unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 37882@debbugs.gnu.org
Subject: bug#37882: [PATCH] build-system/linux-module: Accept a #:make-flags keyword.
Date: Sun, 27 Oct 2019 10:18:06 +0200	[thread overview]
Message-ID: <20191027081806.GA1540@E5400> (raw)
In-Reply-To: <20191025193731.4794-1-me@tobias.gr>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Fri, Oct 25, 2019 at 09:37:31PM +0200, Tobias Geerinckx-Rice via Bug reports for GNU Guix wrote:
> * guix/build-system/linux-module.scm (linux-module-build): Accept a
> MAKE-FLAGS argument.
> <builder>: Pass it on.
> ---
> 
> Efraim,
> 
> Is this in any way related to the topic coming up on IRC last week, or just a coincidence?
> 
> In any case, I'd written the following simple fix but never merged it because I have yet to meet a module with a legitimate need for it.  It works, though.
> 

I thought I had a use-case for it but it turns out I'm pretty sure I
didn't need it in the end. It was more of surprise that it was in one
place and not another.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-27  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  8:06 bug#37882: linux-module-build-system doesn't accept make-flags Efraim Flashner
2019-10-25 19:37 ` bug#37882: [PATCH] build-system/linux-module: Accept a #:make-flags keyword Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-27  8:18   ` Efraim Flashner [this message]
2019-11-04  6:26     ` Danny Milosavljevic
2019-12-04  9:28   ` Efraim Flashner

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191027081806.GA1540@E5400 \
    --to=efraim@flashner.co.il \
    --cc=37882@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).