From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] procps: don't print error message with kernel 3.0+
Date: Tue, 03 Apr 2012 14:53:48 -0700 [thread overview]
Message-ID: <4F7B716C.8060506@linux.intel.com> (raw)
In-Reply-To: <1332884004-5175-1-git-send-email-obi@opendreambox.org>
On 03/27/2012 02:33 PM, Andreas Oberritter wrote:
> * All procps tools print a message like this when the kernel
> version consists of only two numbers:
>
> | Non-standard uts for running kernel:
> | release ... gives version code ...
>
> * Import a patch from Debian to quieten this message.
>
> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
> ---
> .../procps/procps-3.2.8/gnu-kbsd-version.patch | 44 ++++++++++++++++++++
> meta/recipes-extended/procps/procps_3.2.8.bb | 3 +-
> 2 files changed, 46 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-extended/procps/procps-3.2.8/gnu-kbsd-version.patch
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-04-03 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 21:33 [PATCH] procps: don't print error message with kernel 3.0+ Andreas Oberritter
2012-04-03 21:53 ` Saul Wold [this message]
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=4F7B716C.8060506@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 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.