linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [FAILURE] omap4430-sdp allnoconfig
Date: Fri, 2 Aug 2013 13:56:49 -0700	[thread overview]
Message-ID: <20130802205649.GB8296@codeaurora.org> (raw)
In-Reply-To: <CAOesGMhs2osur+VixuyknEWDNy9ekp=yY_6J40W_qRN1TsFWBA@mail.gmail.com>

On 08/02, Olof Johansson wrote:
> On Fri, Aug 2, 2013 at 1:44 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> > On 08/01, Olof Johansson wrote:
> >> On Thu, Aug 01, 2013 at 11:59:56AM -0700, Stephen Boyd wrote:
> >> > On 08/01, Santosh Shilimkar wrote:
> >> > > This one looks fine for me. Can you send above in
> >> > > a proper patch ? Let me know if you want me to
> >> > > send it.
> >> > >
> >> >
> >> > Here's a proper patch. Olof, can you please apply this on top of
> >> > the merge (and maybe you can fix the merge again to handle the
> >> > HAVE_CAN problem I mentioned earlier).
> >> >
> >> > ---8<---
> >> > Subject: [PATCH] ARM: OMAP2+: Fix fallout from localtimer divorce and SMP=n
> >> >
> >> > A recent patch ef3160c (ARM: OMAP2+: Divorce from local timer
> >> > API, 2013-03-04) broke the omap build when SMP=n because the TWD
> >> > functions are only compiled on SMP=y builds. Stub out the TWD
> >> > calls when the TWD isn't built in to to keep everything building.
> >> >
> >> > arch/arm/mach-omap2/built-in.o: In function
> >> > `omap4_local_timer_init':
> >> > dss-common.c:(.init.text+0x1d90): undefined reference to
> >> > `twd_local_timer_register'
> >> >
> >> > Reported-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> >> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >> > Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> >>
> >> Thanks, applied (with the reported-by changed as requested)
> >>
> >
> > It looks like somehow you became the author. Is there anyway you
> > can fix that and possibly fix the merge before it to not add
> > HAVE_CAN_FLEXCAN if CAN in mach-imx/Kconfig?
> 
> That's because the patch wasn't sent such that it could be applied
> with git am, and forgot to set authorship back. Fixed now.
> 

Ah sorry, I thought you would use git am --scissors so it would
keep the authorship from the sender. I'll just add From: in
future scissored patches to make this simpler.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-08-02 20:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 17:52 [FAILURE] omap4430-sdp allnoconfig Russell King - ARM Linux
2013-08-01 18:11 ` Santosh Shilimkar
2013-08-01 18:27   ` Russell King - ARM Linux
2013-08-01 18:31     ` Santosh Shilimkar
2013-08-01 18:34       ` Stephen Boyd
2013-08-01 18:37         ` Stephen Boyd
2013-08-01 18:48           ` Santosh Shilimkar
2013-08-01 18:59             ` Stephen Boyd
2013-08-01 19:01               ` Santosh Shilimkar
2013-08-01 19:02               ` Russell King - ARM Linux
2013-08-01 20:06               ` Olof Johansson
2013-08-02 20:44                 ` Stephen Boyd
2013-08-02 20:50                   ` Olof Johansson
2013-08-02 20:56                     ` Stephen Boyd [this message]
2013-08-02 20:59                       ` Olof Johansson

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=20130802205649.GB8296@codeaurora.org \
    --to=sboyd@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).