From: Mason <slash.tmp@free.fr>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media <linux-media@vger.kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: Automatic device driver back-porting with media_build
Date: Thu, 17 Dec 2015 18:03:18 +0100 [thread overview]
Message-ID: <5672EAD6.2000706@free.fr> (raw)
In-Reply-To: <20151217140943.7048811b@recife.lan>
On 17/12/2015 17:09, Mauro Carvalho Chehab wrote:
> As I said before, heavily patched Kernel. It seems that the network stack
> was updated to some newer version. The media_build backport considers
> only the upstream Kernels. In the specific case of 3.4, it is known
> to build fine with Kernel linux-3.4.27. See:
> http://hverkuil.home.xs4all.nl/logs/Wednesday.log
I don't think the network stack is different from vanilla...
I had a different idea:
The media_build process prints:
"Preparing to compile for kernel version 3.4.3913"
In fact, the custom kernel's Makefile contains:
VERSION = 3
PATCHLEVEL = 4
SUBLEVEL = 39
EXTRAVERSION = 13
NAME = Saber-toothed Squirrel
Is it possible that the build process gets confused by the EXTRAVERSION field?
Regards.
next prev parent reply other threads:[~2015-12-17 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 12:13 Automatic device driver back-porting with media_build Mason
2015-12-17 12:55 ` Mauro Carvalho Chehab
2015-12-17 13:52 ` Mason
2015-12-17 14:08 ` Mauro Carvalho Chehab
2015-12-17 14:30 ` Mason
2015-12-17 14:55 ` Mauro Carvalho Chehab
2015-12-17 15:32 ` Mason
2015-12-17 16:09 ` Mauro Carvalho Chehab
2015-12-17 16:48 ` Mason
2015-12-18 10:37 ` Mauro Carvalho Chehab
2015-12-18 11:01 ` Mason
2015-12-17 17:03 ` Mason [this message]
2015-12-17 17:17 ` Mason
2015-12-18 10:44 ` Mason
2015-12-18 11:03 ` Mauro Carvalho Chehab
2015-12-18 11:22 ` Mauro Carvalho Chehab
2015-12-18 12:10 ` Mason
2015-12-18 12:59 ` Mason
2015-12-18 13:40 ` Mason
2015-12-18 15:13 ` Mason
2015-12-18 17:10 ` Mason
2015-12-18 19:42 ` Mason
2015-12-28 10:44 ` Mason
2015-12-28 12:21 ` Mason
2015-12-28 13:02 ` Mauro Carvalho Chehab
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=5672EAD6.2000706@free.fr \
--to=slash.tmp@free.fr \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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 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).