From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
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:18:32 +0100 [thread overview]
Message-ID: <54EF1D28.8020503@broadcom.com> (raw)
In-Reply-To: <54EF1C05.2000901@broadcom.com>
On 02/26/15 14:13, Arend van Spriel wrote:
> On 02/26/15 14:05, Johannes Berg wrote:
>> On Thu, 2015-02-26 at 13:49 +0100, Arend van Spriel wrote:
>>> When attempting to build backport package the error message
>>> "Kernel version parse failed" popped up. Realizing the machine
>>> was already running a 4.0-rc1 kernel, this patch fixes the
>>> issue. At least until kernel 9.x it will.
>>
>> Is this really enough? we also generate those kernel version Kconfig
>> symbols for dependencies - I htink that needs to be adjusted as well.
>
> Will double-check the results. Building it worked without issues, but it
> could be due to the fact that backport and target kernel versions are
> the same. You made me a bit wary to actually load the modules, but I
> will do it anyway ;-)
Seems to be really enough for this (unlikely) scenario.
Regards,
Arend
> Arend
>
>> johannes
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-26 13:18 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 [this message]
2015-02-26 13:20 ` Johannes Berg
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=54EF1D28.8020503@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--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