linux-kernel - Re: [PATCH v3 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]

Message-ID: <20141029232740.GA4063@kroah.com>
Date:	Wed, 29 Oct 2014 16:27:40 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Fabio Falzoi <fabio.falzoi84@...il.com>
Cc:	micky_ching@...lsil.com.cn, dan.carpenter@...cle.com,
	joe@...ches.com, giedrius.statkevicius@...il.com,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] Staging: rts5208: rtsx_reset_chip style clean up

On Wed, Oct 29, 2014 at 10:58:17PM +0100, 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 295 and 313
> 
> 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
> 
> Changes in v3:
> * rebased against master branch of linux-next tree

That's not going to work, can you redo it against my staging-testing
branch of staging.git?  Or, if you really want to work off of
linux-next, wait a few days before I merge my staging-testing branch
into staging-next to show up in linux-next.

As it is, these patches don't apply, so I'm going to have to drop them
from my queue.

thanks,

greg k-h
--
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/