All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: navin patidar <navin.patidar@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 06/13] staging: rtl8188eu: Remove unused funtion _rtw_read_mem()
Date: Tue, 10 Jun 2014 10:28:24 +0300	[thread overview]
Message-ID: <20140610072824.GH5500@mwanda> (raw)
In-Reply-To: <1402071320-14400-5-git-send-email-navin.patidar@gmail.com>

Thanks.  This is much nicer to review when they are all folded together
like this.

regards,
dan carpenter


  reply	other threads:[~2014-06-10  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 16:15 [PATCH 02/13] staging: rtl8188eu: Remove rtw_deinit_intf_priv() navin patidar
2014-06-06 16:15 ` [PATCH 03/13] staging: rtl8188eu: Remove rtw_init_intf_priv() navin patidar
2014-06-06 16:15 ` [PATCH 04/13] staging: rtl8188eu:Move rtw_hw_[suspend,resume]() to rtw_pwrctrl.c navin patidar
2014-06-06 16:15 ` [PATCH 05/13] staging: rtl8188eu: Remove unused struct intf_priv navin patidar
2014-06-06 16:15 ` [PATCH 06/13] staging: rtl8188eu: Remove unused funtion _rtw_read_mem() navin patidar
2014-06-10  7:28   ` Dan Carpenter [this message]
2014-06-11  4:13     ` navin patidar
2014-06-06 16:15 ` [PATCH 07/13] staging: rtl8188eu: Remove unused function _rtw_write_mem() navin patidar
2014-06-06 16:15 ` [PATCH 08/13] staging: rtl8188eu: Remove unused function declaration and macro navin patidar
2014-06-06 16:15 ` [PATCH 09/13] staging: rtl8188eu: rtw_io.h: Remove unused structures navin patidar
2014-06-06 16:15 ` [PATCH 10/13] staging: rtl8188eu: HalPhyRf_8188e.c: Remove unused macro navin patidar
2014-06-06 16:15 ` [PATCH 11/13] staging: rtl8188eu: HalPhyRf_8188e.c: Remove unnecessary comments navin patidar
2014-06-06 16:15 ` [PATCH] staging: rtl8188eu: os_dep: usb_intf.c: Cleaning up unnecessary code navin patidar
2014-06-06 16:47   ` navin patidar

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=20140610072824.GH5500@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=navin.patidar@gmail.com \
    /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.