From: Ajay Singh <ajay.kathat@microchip.com>
To: Claudiu Beznea <Claudiu.Beznea@microchip.com>
Cc: <linux-wireless@vger.kernel.org>, <devel@driverdev.osuosl.org>,
<gregkh@linuxfoundation.org>, <ganesh.krishna@microchip.com>,
<venkateswara.kaja@microchip.com>, <aditya.shankar@microchip.com>
Subject: Re: [PATCH 02/12] staging: wilc1000: fix too many leading tabs warning in sdio_clear_int_ext()
Date: Wed, 21 Feb 2018 21:55:54 +0530 [thread overview]
Message-ID: <20180221215554.4f38c3e5@ajaysk-VirtualBox> (raw)
In-Reply-To: <7576dfcf-caab-3b2d-c4bb-e1ea29db2fce@microchip.com>
Hi Claudiu,
On Mon, 19 Feb 2018 15:33:09 +0200
Claudiu Beznea <Claudiu.Beznea@microchip.com> wrote:
> Since you re-factor this, as I suggested in patch:
> "[PATCH 6/6] staging: wilc1000: fix line over 80 chars in
> wilc_spi_clear_int_ext()" form your previous series:
> "fix line over 80 char & coding style in wilc_spi.c",
> for code starting here:
Submitted a new patch "[PATCH 3/4] staging: wilc1000: refactor
wilc_spi_clear_int_ext() by using GENMASK macro"
&
"[PATCH 4/4] staging: wilc1000: refactor sdio_clear_int_ext()
by using GENMASK macro" which contain changes as suggested.
>
> and ending here, further improvements could be done. Since the current series
> was accepted, maybe add these to a todo list and review them later?
For both SPI and SDIO the changes are done. Please review and let me know
if you any inputs.
regards,
ajay
next prev parent reply other threads:[~2018-02-21 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 15:11 [PATCH 00/12] fix to remove line over 80 chars and few other Ajay Singh
2018-02-16 15:11 ` [PATCH 01/12] staging: wilc1000: remove unnecessary comments to avoid line over 80 char issue Ajay Singh
2018-02-16 15:11 ` [PATCH 02/12] staging: wilc1000: fix too many leading tabs warning in sdio_clear_int_ext() Ajay Singh
2018-02-19 13:33 ` Claudiu Beznea
2018-02-21 16:25 ` Ajay Singh [this message]
2018-02-21 16:33 ` Claudiu Beznea
2018-02-16 15:11 ` [PATCH 03/12] staging: wilc1000: fix line over 80 characters " Ajay Singh
2018-02-16 15:11 ` [PATCH 04/12] staging: wilc1000: fix open parenthesis alignment mismatch in wilc_parse_network_info() Ajay Singh
2018-02-19 8:56 ` Dan Carpenter
2018-02-16 15:11 ` [PATCH 05/12] staging: wilc1000: fix line over 80 char in wilc_wlan_cfg_set_str() Ajay Singh
2018-02-16 15:11 ` [PATCH 06/12] staging: wilc1000: remove blank line before close brace in wilc_wlan_cfg_get_wid_value() Ajay Singh
2018-02-16 15:11 ` [PATCH 07/12] staging: wilc1000: fix line over 80 chars in wilc_wlan_cfg_indicate_rxi() Ajay Singh
2018-02-16 15:11 ` [PATCH 08/12] staging: wilc1000: fix line over 80 chars in wilc_wlan_cfg_get_wid_value() Ajay Singh
2018-02-16 15:11 ` [PATCH 09/12] staging: wilc1000: fix line over 80 chars in add_tcp_pending_ack() Ajay Singh
2018-02-16 15:11 ` [PATCH 10/12] staging: wilc1000: fix line over 80 characters in tcp_process() Ajay Singh
2018-02-16 15:11 ` [PATCH 11/12] staging: wilc1000: fix line over 80 chars in wilc_wlan_txq_filter_dup_tcp_ack() Ajay Singh
2018-02-19 13:41 ` Claudiu Beznea
2018-02-16 15:11 ` [PATCH 12/12] staging: wilc1000: fix line over 80 chars in wilc_wlan_handle_txq() Ajay Singh
2018-02-16 16:30 ` [PATCH 00/12] fix to remove line over 80 chars and few other Greg KH
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=20180221215554.4f38c3e5@ajaysk-VirtualBox \
--to=ajay.kathat@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=venkateswara.kaja@microchip.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 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).