All of lore.kernel.org
 help / color / mirror / Atom feed
From: <gerg@snapgear.com>
To: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org
Subject: [PATCH 0/2] m68knommu: fix cpu optimization conditionals
Date: Fri, 3 Jun 2011 16:43:15 +1000	[thread overview]
Message-ID: <1307083397-9994-2-git-send-email-gerg@snapgear.com> (raw)
In-Reply-To: <1307083397-9994-1-git-send-email-gerg@snapgear.com>

The next 2 patches improve the conditional checks for portions of cpu
optimized code. Older versions of gcc compiler can incorrectly define
CPU symbols. By using our own local CPU family defines we can also
make the optimizations safe in case of a kernel being compiled for
multiple CPU targets.

  reply	other threads:[~2011-06-03  6:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  6:43 [PATCH 0/2] m68knommu: fix cpu optimization conditionals gerg
2011-06-03  6:43 ` gerg [this message]
2011-06-03  6:43 ` [PATCH 1/2] m68knommu: create config options for CPU classes gerg
2011-06-03 11:15   ` Geert Uytterhoeven
2011-06-06  1:49     ` Greg Ungerer
2011-06-10  3:56     ` Greg Ungerer
2011-06-12  9:36       ` Geert Uytterhoeven
2011-06-23  1:35     ` Greg Ungerer
2011-06-03  6:43 ` [PATCH 2/2] m68k: use kernel processor defines for conditional optimizations gerg

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=1307083397-9994-2-git-send-email-gerg@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.