From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>, backports@vger.kernel.org
Subject: Re: [PATCH] backports: allow building backports package on 4.0+ kernel
Date: Thu, 26 Feb 2015 14:20:29 +0100 [thread overview]
Message-ID: <1424956829.1885.27.camel@sipsolutions.net> (raw)
In-Reply-To: <54EF1D28.8020503@broadcom.com>
On Thu, 2015-02-26 at 14:18 +0100, Arend van Spriel wrote:
> Seems to be really enough for this (unlikely) scenario.
I think it'll be fine until somebody puts
SOME_SYMBOL 4.0
into the dependencies file.
I guess you could try that with some random symbol and see what happens?
I think it would never be selectable.
johannes
next prev parent reply other threads:[~2015-02-26 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 12:49 [PATCH] backports: allow building backports package on 4.0+ kernel Arend van Spriel
2015-02-26 13:05 ` Johannes Berg
2015-02-26 13:13 ` Arend van Spriel
2015-02-26 13:18 ` Arend van Spriel
2015-02-26 13:20 ` Johannes Berg [this message]
2015-03-04 9:06 ` [PATCH] backports: add support for 4.x kernels Luca Coelho
2015-03-04 9:14 ` Johannes Berg
2015-04-03 21:36 ` Hauke Mehrtens
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=1424956829.1885.27.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=mcgrof@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