All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Qais Yousef <qais.yousef@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] mips/include/asm/mipsregs.h: s/u16/unsigned short/
Date: Fri, 06 Dec 2013 08:32:07 -0800	[thread overview]
Message-ID: <52A1FC07.8030902@gmail.com> (raw)
In-Reply-To: <1386321659-30073-1-git-send-email-qais.yousef@imgtec.com>

On 12/06/2013 01:20 AM, Qais Yousef wrote:
> I was getting this error when including this header in my driver:
>
>    arch/mips/include/asm/mipsregs.h:644:33: error: unknown type name ‘u16’
>
> since the use of u16 is not really necessary, convert it to unsigned short.
>
> Signed-off-by: Qais Yousef <qais.yousef@imgtec.com>
> Reviewed-by: Steven J. Hill <Steven.Hill@imgtec.com>

NAK.

Just #include <linux/types.h> at the top of asm/mipsregs.h instead.

David Daney


> ---
>   arch/mips/include/asm/mipsregs.h |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/include/asm/mipsregs.h b/arch/mips/include/asm/mipsregs.h
> index e033141..0a2d6ef 100644
> --- a/arch/mips/include/asm/mipsregs.h
> +++ b/arch/mips/include/asm/mipsregs.h
> @@ -641,9 +641,9 @@
>    * microMIPS instructions can be 16-bit or 32-bit in length. This
>    * returns a 1 if the instruction is 16-bit and a 0 if 32-bit.
>    */
> -static inline int mm_insn_16bit(u16 insn)
> +static inline int mm_insn_16bit(unsigned short insn)
>   {
> -	u16 opcode = (insn >> 10) & 0x7;
> +	unsigned short opcode = (insn >> 10) & 0x7;
>
>   	return (opcode >= 1 && opcode <= 3) ? 1 : 0;
>   }
>

  reply	other threads:[~2013-12-06 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06  9:20 [PATCH] mips/include/asm/mipsregs.h: s/u16/unsigned short/ Qais Yousef
2013-12-06  9:20 ` Qais Yousef
2013-12-06 16:32 ` David Daney [this message]
2013-12-06 16:35   ` Qais Yousef
2013-12-06 16:47     ` David Daney
2013-12-09  9:35       ` Qais Yousef
2013-12-09 18:47         ` David Daney

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=52A1FC07.8030902@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=qais.yousef@imgtec.com \
    /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.