linux-kernel - Re: [PATCH 0/2] Staging: rts5208: rtsx_reset

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] [day] [month] [year] [list]

Date:	Sun, 19 Oct 2014 13:48:51 +0300
From:	Giedrius Statkevicius <giedrius.statkevicius@...il.com>
To:	Fabio Falzoi <fabio.falzoi84@...il.com>, gregkh@...uxfoundation.org
CC:	micky_ching@...lsil.com.cn, joe@...ches.com,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Staging: rts5208: rtsx_reset_chip style clean up

On 2014.10.19 12:55, Fabio Falzoi wrote:
> Clean up the code in rtsx_reset_chip function defining two new helper
> functions rtsx_reset_aspm and rtsx_enable_pcie_intr.
> Specifically, the following checkpatch warnings are corrected:
> * PARENTHESIS_ALIGNMENT at rows 271, 302, 343 and 346
> * LONG_LINE at rows 294, 313 and 315
> * BRACES at rowa 320 and 351
> This patch is inspired by the following post on LKML regarding another
> clean up for rts5208 module:
> http://www.spinics.net/lists/linux-driver-devel/msg55038.html
> 
> Fabio Falzoi (2):
>   Staging: rts5208: helper function to manage aspm during reset
>   Staging: rts5208: helper function to enable interrupts during reset
> 
>  drivers/staging/rts5208/rtsx_chip.c | 168 +++++++++++++++++++-----------------
>  1 file changed, 87 insertions(+), 81 deletions(-)
> 
Could you please remake this patch set against the staging-testing
branch? 
https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/commit/?h=staging-testing&id=ccf2d2456648ce84090ea1f37bd6774bafa99f00
This will break your patch on staging-testing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/