Linux SNPS ARC Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return
Date: Thu, 28 Jan 2016 14:20:37 +0000	[thread overview]
Message-ID: <1453990837.4304.15.camel@synopsys.com> (raw)
In-Reply-To: <56A123CD.1060706@synopsys.com>

Hi Carlos,

On Thu, 2016-01-21@18:30 +0000, Carlos Palminha wrote:
> hi...
> 
> i just found that its blocking waiting for console_lock...
> @vineet, alexey: i think that console_lock is architecture dependent right? Do you know any issue with console_lock
> for ARC?

I'm not really sure "console_lock" has something to do with ARC architecture.
At least "git grep bconsole_lock" doesn't find anything in "arch/arc".

So I'd assume this is a generic thing.

-Alexey

  parent reply	other threads:[~2016-01-28 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5684268E.2000607@synopsys.com>
     [not found] ` <CAGd==071hzpQKjLU715tc004NN0d8Z01XdLAhg-DBx1FxtWb2w@mail.gmail.com>
     [not found]   ` <569CF78F.7050303@synopsys.com>
     [not found]     ` <569CFA9B.4060108@synopsys.com>
     [not found]       ` <CAGd==07ffJAfAtzirALR3OF7f4UDVu_fJbbZ0ZiEa3F5-hLfyw@mail.gmail.com>
     [not found]         ` <569E5E51.8000303@synopsys.com>
     [not found]           ` <569E69EB.3010003@synopsys.com>
     [not found]             ` <CAGd==04VMKUvb6hZkeNw3kAQt04y0d_Ry7oCtC8=2SWcfWG25A@mail.gmail.com>
     [not found]               ` <56A11EF1.3070004@synopsys.com>
2016-01-21 18:30                 ` Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return Carlos Palminha
2016-01-22  8:32                   ` Daniel Stone
2016-01-28 14:20                   ` Alexey Brodkin [this message]
2016-01-28 15:42                     ` Rob Clark

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=1453990837.4304.15.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=linux-snps-arc@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