linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 REPOST 0/5] ARM: omap[34]: Thumb-2 compatibility fixes
Date: Fri, 4 Mar 2011 23:08:17 +0530	[thread overview]
Message-ID: <7b1ef0e49e8b8c1c20b0965a58c4fe73@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimz0Ko9GFtLTcBQVV_c2DAPU5XhV47xT+R9Q7mv@mail.gmail.com>

Dave,
> -----Original Message-----
> From: Dave Martin [mailto:dave.martin at linaro.org]
> Sent: Friday, March 04, 2011 11:05 PM
> To: linux-arm-kernel at lists.infradead.org
> Cc: patches at linaro.org; Tony Lindgren; Santosh Shilimkar; Jean
> Pihet; Kevin Hilman; linux-omap at vger.kernel.org; Nicolas Pitre;
> linaro-dev at lists.linaro.org
> Subject: Re: [PATCH v5 REPOST 0/5] ARM: omap[34]: Thumb-2
> compatibility fixes
>
> On Fri, Mar 4, 2011 at 3:33 PM, Dave Martin <dave.martin@linaro.org>
> wrote:
> > This set of patches, along with some other patches under
> > discussion on alkml, should enable omap3 and omap4 kernels to be
> > built with CONFIG_THUMB2_KERNEL.
> >
> > This patch set builds on recent cleanup done by the omap
> > maintainers.
> >
> > At least some of this code definitely works, most features have
> > been tested successfully. ?Further testing, especially of Thumb-2
> > behaviour, is still welcome.
> >
> > In particular, I still have no Ack/Tested-by on the following
> > patches, so it would be great if anyone who has an opportunity
> > to do a final review / re-test can do so.
> >
> > ?* ARM: omap3: Convert END() to ENDPROC() for correct linkage with
> CONFIG_THUMB2_KERNEL
> > ?* ARM: omap3: Thumb-2 compatibility for sram34xx.S
> > ?* ARM: omap3: Thumb-2 compatibility for sleep34xx.S
>
> Following up on this, it looks like I have some locally-recorded
> acks
> which didn't make it into my posting ...
>
> The one patch I currently have no feedback on is this one:
>
>   * ARM: omap4: Provide do_wfi() for Thumb-2
>
You can drop this one since do_wfi()  won't be needed
anymore after my recent series.

http://www.spinics.net/lists/linux-omap/msg46495.html

  reply	other threads:[~2011-03-04 17:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 15:33 [PATCH v5 REPOST 0/5] ARM: omap[34]: Thumb-2 compatibility fixes Dave Martin
2011-03-04 15:33 ` [PATCH v5 1/5] ARM: omap4: Provide do_wfi() for Thumb-2 Dave Martin
2011-03-04 15:33 ` [PATCH v5 2/5] ARM: omap4: Convert END() to ENDPROC() for correct linkage with CONFIG_THUMB2_KERNEL Dave Martin
2011-03-04 15:33 ` [PATCH v5 3/5] ARM: omap3: Remove hand-encoded SMC instructions Dave Martin
2011-03-04 15:33 ` [PATCH v5 4/5] ARM: omap3: Thumb-2 compatibility for sram34xx.S Dave Martin
2011-03-04 15:33 ` [PATCH v5 5/5] ARM: omap3: Thumb-2 compatibility for sleep34xx.S Dave Martin
2011-03-04 17:35 ` [PATCH v5 REPOST 0/5] ARM: omap[34]: Thumb-2 compatibility fixes Dave Martin
2011-03-04 17:38   ` Santosh Shilimkar [this message]
2011-03-04 17:47     ` Tony Lindgren
2011-03-04 18:16       ` Dave Martin
2011-03-04 21:42         ` Kevin Hilman
2011-03-04 21:55           ` Nicolas Pitre
2011-03-07 10:26           ` Dave Martin
2011-03-07 21:35     ` Kevin Hilman
2011-03-08  5:53       ` Santosh Shilimkar
2011-03-07 22:09 ` Kevin Hilman

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=7b1ef0e49e8b8c1c20b0965a58c4fe73@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --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).