linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Linux on Toradex Colibri PXA320
Date: Fri, 11 Dec 2009 20:09:24 +0000	[thread overview]
Message-ID: <20091211200924.GA12628@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <52701260536728@webmail34.yandex.ru>

On Fri, Dec 11, 2009 at 04:05:28PM +0300, Dennis Semakin wrote:
> Hello everbody
> 
> Excuse me, but I want to ask you a something.

The very first you need to fix is whatever you're using to get these
kernel messages out.  It's clearly introducing corruption; there's
absolutely no need to print "kernel/printk.c" before every message
for starters, and it looks like that is overwriting some of the
original message.

Once you've sorted that problem out, please re-post.

  reply	other threads:[~2009-12-11 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 13:05 Linux on Toradex Colibri PXA320 Dennis Semakin
2009-12-11 20:09 ` Russell King - ARM Linux [this message]
2009-12-11 23:05   ` Dennis Semakin

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=20091211200924.GA12628@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).