From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: add 1.21.x series
Date: Mon, 21 Jan 2013 23:56:00 +0100 [thread overview]
Message-ID: <87a9s26t8f.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50FDC43E.5020903@zacarias.com.ar> (Gustavo Zacarias's message of "Mon, 21 Jan 2013 19:42:06 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> On 01/21/2013 07:39 PM, Peter Korsgaard wrote:
>> Ahh come on, don't like my syslog-to-kmsg feature? ;)
Gustavo> Hahaha :)
Gustavo> Kernel 3.5+ doesn't sound friendly with some of the same
Gustavo> configurations like qemu-sh4-r2d (blame Qemu for lack of FIFO
Gustavo> support that kernels newer than 3.2.x use). Regards.
3.5+ support is only needed to be able to store the full syslog facility
in the kernel log. It still works (with level only) on earlier kernels.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-21 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 22:14 [Buildroot] [PATCH] busybox: add 1.21.x series Gustavo Zacarias
2013-01-21 22:39 ` Peter Korsgaard
2013-01-21 22:42 ` Gustavo Zacarias
2013-01-21 22:56 ` Peter Korsgaard [this message]
2013-01-21 23:01 ` Gustavo Zacarias
2013-01-21 23:10 ` Peter Korsgaard
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=87a9s26t8f.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox