All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rabin Vincent <rabin@rab.in>
To: jesper.nilsson@axis.com
Cc: linux-kernel@vger.kernel.org, linux-cris-kernel@axis.com,
	Rabin Vincent <rabin@rab.in>
Subject: [PATCH 2/8] CRIS: UAPI: use generic auxvec.h
Date: Thu, 14 May 2015 17:28:06 +0200	[thread overview]
Message-ID: <1431617292-10067-2-git-send-email-rabin@rab.in> (raw)
In-Reply-To: <1431617292-10067-1-git-send-email-rabin@rab.in>

CRIS's auxvec.h is empty just like the asm-generic version.

Effective diff:

 @@ -1,4 +1,5 @@
 -#ifndef __ASMCRIS_AUXVEC_H
 -#define __ASMCRIS_AUXVEC_H
 +#ifndef __ASM_GENERIC_AUXVEC_H
 +#define __ASM_GENERIC_AUXVEC_H
 +

  #endif

Signed-off-by: Rabin Vincent <rabin@rab.in>
---
 arch/cris/include/asm/Kbuild | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/cris/include/asm/Kbuild b/arch/cris/include/asm/Kbuild
index c1d6da9..161bbf7 100644
--- a/arch/cris/include/asm/Kbuild
+++ b/arch/cris/include/asm/Kbuild
@@ -1,4 +1,5 @@
 generic-y += atomic.h
+generic-y += auxvec.h
 generic-y += barrier.h
 generic-y += bitsperlong.h
 generic-y += clkdev.h
-- 
2.1.4


  reply	other threads:[~2015-05-14 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 15:28 [PATCH 1/8] CRIS: UAPI: use generic headers via Kbuild Rabin Vincent
2015-05-14 15:28 ` Rabin Vincent [this message]
2015-05-14 15:28 ` [PATCH 3/8] CRIS: UAPI: use generic sockios.h Rabin Vincent
2015-05-14 15:28 ` [PATCH 4/8] CRIS: UAPI: use generic sembuf.h Rabin Vincent
2015-05-14 15:28 ` [PATCH 5/8] CRIS: UAPI: use generic socket.h Rabin Vincent
2015-05-14 15:28 ` [PATCH 6/8] CRIS: UAPI: use generic msgbuf.h Rabin Vincent
2015-05-14 15:28 ` [PATCH 7/8] CRIS: UAPI: use generic shmbuf.h Rabin Vincent
2015-05-14 15:28 ` [PATCH 8/8] CRIS: UAPI: use generic types.h Rabin Vincent

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=1431617292-10067-2-git-send-email-rabin@rab.in \
    --to=rabin@rab.in \
    --cc=jesper.nilsson@axis.com \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.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.