From: "Luís Henriques" <luis.henriques@canonical.com>
To: Qais Yousef <Qais.Yousef@imgtec.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
"Ralf Baechle (ralf@linux-mips.org)" <ralf@linux-mips.org>
Subject: Re: [PATCH v2] mips/include/asm/mipsregs.h: include linux/types.h
Date: Thu, 20 Mar 2014 11:06:38 +0000 [thread overview]
Message-ID: <20140320110638.GC3709@hercules> (raw)
In-Reply-To: <392C4BDEFF12D14FA57A3F30B283D7D14152C8@LEMAIL01.le.imgtec.org>
On Fri, Mar 14, 2014 at 12:08:13PM +0000, Qais Yousef wrote:
> Can we include this patch in the next 3.10 and forward stable releases please?
>
> It's already in Linus' tree under commit id: 87c99203fea897fbdd84b681ad9fced2517dcf98
>
> Thanks,
> Qais
Thank you, I'm queuing it for the 3.11 kernel.
Cheers,
--
Luís
> > -----Original Message-----
> > From: Qais Yousef
> > Sent: 09 December 2013 09:50
> > To: linux-mips@linux-mips.org
> > Cc: Qais Yousef
> > Subject: [PATCH v2] mips/include/asm/mipsregs.h: include linux/types.h
> >
> > The file uses u16 type but doesn't include its definition explicitly
> >
> > 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’
> >
> > Signed-off-by: Qais Yousef <qais.yousef@imgtec.com>
> > Reviewed-by: Steven J. Hill <Steven.Hill@imgtec.com>
> > ---
> > changes since v1:
> > - include linux/types.h instead of s/u16/unsigned short/
> > - amend commit message accordingly
> >
> > arch/mips/include/asm/mipsregs.h | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/mips/include/asm/mipsregs.h
> > b/arch/mips/include/asm/mipsregs.h
> > index e033141..86479bb 100644
> > --- a/arch/mips/include/asm/mipsregs.h
> > +++ b/arch/mips/include/asm/mipsregs.h
> > @@ -14,6 +14,7 @@
> > #define _ASM_MIPSREGS_H
> >
> > #include <linux/linkage.h>
> > +#include <linux/types.h>
> > #include <asm/hazards.h>
> > #include <asm/war.h>
> >
> > --
> > 1.7.1
>
prev parent reply other threads:[~2014-03-20 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 9:49 [PATCH v2] mips/include/asm/mipsregs.h: include linux/types.h Qais Yousef
2013-12-09 9:49 ` Qais Yousef
2013-12-09 18:48 ` David Daney
2014-03-14 12:08 ` Qais Yousef
2014-03-14 13:20 ` Ralf Baechle
2014-03-20 11:06 ` Luís Henriques [this message]
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=20140320110638.GC3709@hercules \
--to=luis.henriques@canonical.com \
--cc=Qais.Yousef@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox