public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Venkat Subbiah <vsubbiah@caviumnetworks.com>
To: "frank.rowand@am.sony.com" <frank.rowand@am.sony.com>
Cc: "Subbiah, Venkat" <Venkat.Subbiah@caviumnetworks.com>,
	RT <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: patch to fix early printks with PREMPT_RT_FULL
Date: Mon, 21 May 2012 12:54:15 -0700	[thread overview]
Message-ID: <4FBA9D67.6060608@caviumnetworks.com> (raw)
In-Reply-To: <4FB5A646.7060803@am.sony.com>

On 05/17/2012 06:30 PM, Frank Rowand wrote:
> On 05/17/12 14:33, Venkat Subbiah wrote:
>> Thomas,
>> Is this patch going to make it to a release or should this sent be sent
>> to more folks for review?
>> Thanks,
>> Venkat
>>
>> On 05/04/2012 06:07 PM, Venkat Subbiah wrote:
>>> Hello,
>>>
>>> With PREMPT_RT_FULL I notice couple of issues when early printk is turned on
>>>
>>> 1)  printks show up only after the full console is enabled
>>> 2)  There are double prints for each of the prinkts before the full
>>> console was enabled.
> Venkat,
>
> Do my patches from yesterday solve problem #1 for you?  (I can't
> test for your problem, because I don't see it on my ARM system.)
The patch doe solve both #1 and #2. Thanks.
-Venkat

>
>     http://marc.info/?l=linux-rt-users&m=133721694105947&w=2
>
>     http://marc.info/?l=linux-rt-users&m=133721717706004&w=2
>
> For problem #2, does that also exist without the RT patches?
>
> -Frank
>
>


  reply	other threads:[~2012-05-21 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05  1:07 patch to fix early printks with PREMPT_RT_FULL Venkat Subbiah
2012-05-17 21:33 ` Venkat Subbiah
2012-05-18  1:30   ` Frank Rowand
2012-05-21 19:54     ` Venkat Subbiah [this message]
2012-05-21 20:12     ` Venkat Subbiah

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=4FBA9D67.6060608@caviumnetworks.com \
    --to=vsubbiah@caviumnetworks.com \
    --cc=Venkat.Subbiah@caviumnetworks.com \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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