linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-alpha@vger.kernel.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: alpha boot hang - 4.14-rc* regression
Date: Thu, 26 Oct 2017 09:54:47 +0100	[thread overview]
Message-ID: <20171026085447.GA16024@red-moon> (raw)
In-Reply-To: <alpine.LRH.2.21.1710252100080.16994@math.ut.ee>

On Wed, Oct 25, 2017 at 09:01:07PM +0300, Meelis Roos wrote:
> > It is probably because I patched the wrong map_irq() function,
> > I am trying to detect which one you are _actually_ using, if
> > the patch below fails I will patch them all (which is what I
> > have to do anyway).
> > 
> > Please give this a go - this _has_ to make a difference, it is not
> > correct to leave map_irq() pointers as __init memory, IRQ routing
> > for modules can't work.
> 
> This works for mainline git too.
> 
> If you have another round that fixes all subarches, I will try it on a 
> PC164 too.

Sure, I will send one patch shortly updating all map/swizzle functions
to remove the __init markers.

Thanks,
Lorenzo

      reply	other threads:[~2017-10-26  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  8:05 alpha boot hang - 4.14-rc* regression Meelis Roos
2017-10-25  8:12 ` Meelis Roos
2017-10-25  8:43   ` Meelis Roos
2017-10-25  9:21     ` Lorenzo Pieralisi
2017-10-25 12:21       ` Meelis Roos
2017-10-25 13:37         ` Lorenzo Pieralisi
2017-10-25 14:49           ` Meelis Roos
2017-10-25 15:14             ` Lorenzo Pieralisi
2017-10-25 15:54               ` Meelis Roos
2017-10-25 18:01               ` Meelis Roos
2017-10-26  8:54                 ` Lorenzo Pieralisi [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=20171026085447.GA16024@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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).