From: Greg KH <gregkh@linuxfoundation.org>
To: Fabio Falzoi <fabio.falzoi84@gmail.com>
Cc: micky_ching@realsil.com.cn, dan.carpenter@oracle.com,
joe@perches.com, giedrius.statkevicius@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Staging: rts5208: rtsx_reset_chip style clean up
Date: Wed, 29 Oct 2014 16:27:40 -0700 [thread overview]
Message-ID: <20141029232740.GA4063@kroah.com> (raw)
In-Reply-To: <1414619899-2633-1-git-send-email-fabio.falzoi84@gmail.com>
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
prev parent reply other threads:[~2014-10-29 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 21:58 [PATCH v3 0/2] Staging: rts5208: rtsx_reset_chip style clean up Fabio Falzoi
2014-10-29 21:58 ` [PATCH v3 1/2] Staging: rts5208: helper function to manage aspm during reset Fabio Falzoi
2014-10-29 21:58 ` [PATCH v3 2/2] Staging: rts5208: helper function to enable interrupts Fabio Falzoi
2014-10-29 23:27 ` Greg KH [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=20141029232740.GA4063@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fabio.falzoi84@gmail.com \
--cc=giedrius.statkevicius@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=micky_ching@realsil.com.cn \
/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.