From: Dan Carpenter <dan.carpenter@oracle.com>
To: Fabio Falzoi <fabio.falzoi84@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v2 0/2] Staging: rts5208: rtsx_reset_chip style clean up
Date: Mon, 20 Oct 2014 13:02:49 +0300 [thread overview]
Message-ID: <20141020100249.GK23154@mwanda> (raw)
In-Reply-To: <1413747003-13655-1-git-send-email-fabio.falzoi84@gmail.com>
These look good to me.
Reviewed-by: Dan Carpenter <dan.carpente@oracle.com>
regards,
dan carpenter
prev parent reply other threads:[~2014-10-20 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 19:30 [PATCH v2 0/2] Staging: rts5208: rtsx_reset_chip style clean up Fabio Falzoi
2014-10-19 19:30 ` [PATCH v2 1/2] Staging: rts5208: helper function to manage aspm during reset Fabio Falzoi
2014-10-19 19:30 ` [PATCH v2 2/2] Staging: rts5208: helper function to enable interrupts " Fabio Falzoi
2014-10-20 10:02 ` Dan Carpenter [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=20141020100249.GK23154@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=fabio.falzoi84@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).