mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: jonas@southpole.se
Cc: linux@openrisc.net, linux-kernel@vger.kernel.org,
	Richard Weinberger <richard@nod.at>
Subject: [PATCH 2/5] OpenRISC: Use generic bitops.h
Date: Fri,  2 Mar 2012 01:55:12 +0100	[thread overview]
Message-ID: <1330649715-32438-2-git-send-email-richard@nod.at> (raw)
In-Reply-To: <1330649715-32438-1-git-send-email-richard@nod.at>

There is no need to reinvent the wheel.

Signed-off-by: Richard Weinberger <richard@nod.at>
---
 arch/openrisc/include/asm/Kbuild |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/arch/openrisc/include/asm/Kbuild b/arch/openrisc/include/asm/Kbuild
index 11162e6..a283165 100644
--- a/arch/openrisc/include/asm/Kbuild
+++ b/arch/openrisc/include/asm/Kbuild
@@ -4,6 +4,7 @@ header-y += spr_defs.h
 
 generic-y += atomic.h
 generic-y += auxvec.h
+generic-y += bitops.h
 generic-y += bitsperlong.h
 generic-y += bug.h
 generic-y += bugs.h
-- 
1.7.7.3


  reply	other threads:[~2012-03-02  0:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  0:55 [PATCH 1/5] OpenRISC: Select GENERIC_ATOMIC64 Richard Weinberger
2012-03-02  0:55 ` Richard Weinberger [this message]
2012-03-02  6:50   ` [PATCH 2/5] OpenRISC: Use generic bitops.h Jonas Bonn
2012-03-02  8:47     ` Richard Weinberger
2012-03-02  0:55 ` [PATCH 3/5] OpenRISC: Export memory_start and memory_end Richard Weinberger
2012-03-02  6:51   ` Jonas Bonn
2012-03-02  8:48     ` Richard Weinberger
2012-03-02  9:14       ` Jonas Bonn
2012-03-02  0:55 ` [PATCH 4/5] OpenRISC: Include export.h Richard Weinberger
2012-03-02  0:55 ` [PATCH 5/5] OpenRISC: Export dump_stack() Richard Weinberger
2012-03-02  7:12   ` Jonas Bonn

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=1330649715-32438-2-git-send-email-richard@nod.at \
    --to=richard@nod.at \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@openrisc.net \
    /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

all inboxes | Powered by JetHome®