linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] msm: fix debug-macro.S build failure
Date: Thu, 28 Oct 2010 11:27:38 -0700	[thread overview]
Message-ID: <1288290458.2683.25.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010281422190.3227@xanadu.home>

On Thu, 2010-10-28 at 14:24 -0400, Nicolas Pitre wrote:
> On Thu, 28 Oct 2010, Daniel Walker wrote:
> 
> > This is what the function currently has,
> > 
> >         .macro  addruart, rp, rv
> >         ldr     \rp, =MSM_DEBUG_UART_PHYS
> >         ldr     \rv, =MSM_DEBUG_UART_BASE
> >         .endm
> > 
> > So if we have a MSM_DEBUG_UART_PHYS and MSM_DEBUG_UART_BASE we're
> > returning it. We don't actually have those values for all the boards
> > tho. My understanding was that there are some generic arm changes
> > needed, but I need to confirm that.
> 
> Just return 0 in both registers when you have nothing better to return.

What about the other functions ?

Daniel

-- 

Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2010-10-28 18:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 21:58 [PATCH] msm: fix debug-macro.S build failure Daniel Walker
2010-10-27 22:14 ` Russell King - ARM Linux
2010-10-27 22:25   ` [PATCH -v2] " Daniel Walker
2010-10-28  2:30   ` [PATCH] " Nicolas Pitre
2010-10-28 16:30     ` Daniel Walker
2010-10-28 16:35       ` Russell King - ARM Linux
2010-10-28 16:41         ` Daniel Walker
2010-10-28 17:46           ` Russell King - ARM Linux
2010-10-28 18:00             ` Daniel Walker
2010-10-28 18:24               ` Nicolas Pitre
2010-10-28 18:27                 ` Daniel Walker [this message]
2010-10-28 18:29                   ` Russell King - ARM Linux
2010-10-28 18:46                     ` Nicolas Pitre
2010-10-28 18:40                   ` Nicolas Pitre
2010-10-28 18:28                 ` Russell King - ARM Linux
2010-10-28 18:43                   ` Nicolas Pitre
2010-10-28 18:46                     ` Russell King - ARM Linux
2010-10-29  3:03                       ` Nicolas Pitre
2010-10-29 21:17                         ` Daniel Walker
2010-10-29 22:14                           ` Russell King - ARM Linux
2010-10-29 22:21                             ` Daniel Walker
2010-10-29 22:28                               ` Russell King - ARM Linux
2010-10-29 23:06                             ` [PATCH -v3] " Daniel Walker
2010-10-29 22:17                           ` [PATCH] " Nicolas Pitre
2010-10-29 22:32                             ` Daniel Walker
2010-10-29 22:53                               ` Nicolas Pitre
2010-10-29 23:07                                 ` Daniel Walker
2010-11-05 21:31                                   ` David Brown
2010-10-28 22:36             ` Rohit Vaswani
2010-10-29  2:26               ` Nicolas Pitre

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=1288290458.2683.25.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --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).