lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 28 Jul 2015 14:46:35 +0000
From:	Shenwei Wang <Shenwei.Wang@...escale.com>
To:	Shawn Guo <shawnguo@...nel.org>
CC:	"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"jason@...edaemon.net" <jason@...edaemon.net>,
	"Huang Anson" <Anson.Huang@...escale.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v7 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup
 sources

> -----Original Message-----
> From: Shawn Guo [mailto:shawnguo@...nel.org]
> Sent: 2015年7月28日 9:39
> To: Wang Shenwei-B38339
> Cc: shawn.guo@...aro.org; tglx@...utronix.de; jason@...edaemon.net; Huang
> Yongcai-B20788; linux-kernel@...r.kernel.org;
> linux-arm-kernel@...ts.infradead.org
> Subject: Re: [PATCH v7 1/2] irqchip: imx-gpcv2: IMX GPCv2 driver for wakeup
> sources
> 
> On Tue, Jul 28, 2015 at 02:27:42PM +0000, Shenwei Wang wrote:
> > > > +static int gpcv2_wakeup_source_save(void) {
> > > > +	struct imx_gpcv2_irq *cd;
> > >
> > > We generally name variables in an abbrev of the types to make them
> > > intuitive.  I tried hard to map "cd" to "imx_gpcv2_irq" and failed.
> > > Can you help me on that?
> >
> > CD is the abbreviation of chip data which is a member of irq_data.
> 
> You are defining a variable of type imx_gpcv2_irq, neither chip_data nor irq_data.

Imx_gpcv2_irq itself is the chip_data of irq_data.

> > > > +void ca7_cpu_resume(void);
> > > > +void imx7_suspend(void __iomem *ocram_vbase);
> > >
> > > Why do these declarations need to be in this header?
> >
> > Just to resolve the compile errors.
> 
> Wrong solution.  They belong to some header in arch/arm/mach-imx not
> include/soc/imx, as there is no code outside arch/arm/mach-imx needs these
> declaration.

It is a little ugly. I was thinking to have a gpcv2.h header file, so put them there. 
But as the header file is going to be removed, I am considering to move it to 
common.h. Although it seems not beautiful too.

Thanks,
Shenwei

> Shawn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ