linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tixy@yxit.co.uk (Tixy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Fix Thumb-2 undef handling for mixed-arch kernels
Date: Fri, 19 Aug 2011 10:22:09 +0100	[thread overview]
Message-ID: <1313745729.29336.3.camel@computer2> (raw)
In-Reply-To: <20110819091005.GA2742@arm.com>

On Fri, 2011-08-19 at 10:10 +0100, Dave Martin wrote: 
> On Fri, Aug 19, 2011 at 09:44:28AM +0100, Tixy wrote:
> > On Thu, 2011-08-18 at 23:29 +0100, Russell King - ARM Linux wrote:
> > > On Thu, Aug 18, 2011 at 06:01:51PM +0100, Dave Martin wrote:
> > > > In kernels which support v6 and v7 platforms in a single binary
> > > > such as omap2plus_defconfig for example, undefined instruction
> > > > exceptions taken on Thumb instructions are not processed correctly,
> > > > because the kernel assumes at build-time that Thumb-2 won't be
> > > > supported in userspace.
> > > 
> > > Unless there's any further comments from anyone, I think this is now
> > > ready.  Thanks.
> > 
> > I've no further comments.
> 
> Are you happy for me to transfer your reviewed-by to the new version of
> patch 1?

Yes, I compared the new patch to the old one.

  reply	other threads:[~2011-08-19  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 17:01 [PATCH v2 0/3] Fix Thumb-2 undef handling for mixed-arch kernels Dave Martin
2011-08-18 17:01 ` [PATCH v2 1/3] ARM: Make cpu_architecture into a global variable Dave Martin
2011-08-18 17:01 ` [PATCH v2 2/3] ARM: entry: Remove unnecessary masking when decoding Thumb-2 instructions Dave Martin
2011-08-18 17:01 ` [PATCH v2 3/3] ARM: entry: Fix Thumb-2 undef handling for multi-CPU kernels Dave Martin
2011-08-18 22:29 ` [PATCH v2 0/3] Fix Thumb-2 undef handling for mixed-arch kernels Russell King - ARM Linux
2011-08-19  8:44   ` Tixy
2011-08-19  9:10     ` Dave Martin
2011-08-19  9:22       ` Tixy [this message]
2011-08-19  9:00   ` Dave Martin

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=1313745729.29336.3.camel@computer2 \
    --to=tixy@yxit.co.uk \
    --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).