All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23
Date: Mon, 24 Feb 2014 20:16:24 +0100	[thread overview]
Message-ID: <530B9A88.9010402@mind.be> (raw)
In-Reply-To: <CAAXf6LX0eoYHR7PUb8MvZdJFiQN29Tt8CBf8iFqY8wFa3FFetw@mail.gmail.com>

On 24/02/14 12:37, Thomas De Schampheleire wrote:
> On Mon, Feb 24, 2014 at 11:30 AM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
>>
>>
>>  >> tvheadend-c7d0335eb10d02b78... | 1
>>
>>  > Too old kernel headers (SYS_TURBO), patch available:
>>  > http://patchwork.ozlabs.org/patch/323403/
>>
>> Yes, but that relies on the TOOLCHAIN_HEADERS_AT_LEAST_x stuff. Do we
>> want that for 2014.02?
> 
> It may be very short before the deadline for a patch series like this,
> but if you ask me, I would dare to apply it still.

 I disagree. Even though the patch series just touches Config.in so is
less risky, I think it's a bad idea to still apply it to master now. I
wouldn't like to have to release a 2014.02.1 again...

 Also note that this is not a regression - we've lived with the
incompatible kernel headers situation for years. I think that not fixing
this behaviour in 2014.02 is less bad than running the risk of breaking
something that works.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2014-02-24 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23 Thomas Petazzoni
2014-02-24  8:38 ` Thomas De Schampheleire
2014-02-24 10:30   ` Peter Korsgaard
2014-02-24 11:37     ` Thomas De Schampheleire
2014-02-24 19:16       ` Arnout Vandecappelle [this message]
2014-02-25  5:50         ` Thomas De Schampheleire
2014-02-24 20:37       ` Thomas Petazzoni
2014-02-24 20:44         ` Yann E. MORIN
2014-02-24 20:36   ` Thomas Petazzoni
2014-02-25  5:22     ` Baruch Siach
2014-02-25  5:47       ` Max Filippov
2014-02-25  6:03         ` Baruch Siach
2014-02-25  6:15           ` Max Filippov

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=530B9A88.9010402@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.