From: Ajay Singh <ajay.kathat@microchip.com>
To: <hariprasath.elango@gmail.com>
Cc: <aditya.shankar@microchip.com>, <gregkh@linuxfoundation.org>,
<ganesh.krishna@microchip.com>, <linux-wireless@vger.kernel.org>,
<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/7] staging: wilc1000: remove unwanted braces and correct code alignment
Date: Wed, 14 Mar 2018 19:38:03 +0530 [thread overview]
Message-ID: <20180314193803.39bdd142@ajaysk-VirtualBox> (raw)
In-Reply-To: <31227bdc32df8b76d6a81ca224e1381020f681df.1521030891.git.hariprasath.elango@gmail.com>
On Wed, 14 Mar 2018 18:15:04 +0530
<hariprasath.elango@gmail.com> wrote:
> From: HariPrasath Elango <hariprasath.elango@gmail.com>
>
> Remove the unwated brace and corrected the code block alignment
> accordingly
Changes done in this patch are already taken care. Today, Greg has
applied the patch which had these changes. This patch can be ignore from
the patchset.
Regards,
Ajay
WARNING: multiple messages have this Message-ID (diff)
From: Ajay Singh <ajay.kathat@microchip.com>
To: <hariprasath.elango@gmail.com>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ganesh.krishna@microchip.com, aditya.shankar@microchip.com
Subject: Re: [PATCH 6/7] staging: wilc1000: remove unwanted braces and correct code alignment
Date: Wed, 14 Mar 2018 19:38:03 +0530 [thread overview]
Message-ID: <20180314193803.39bdd142@ajaysk-VirtualBox> (raw)
In-Reply-To: <31227bdc32df8b76d6a81ca224e1381020f681df.1521030891.git.hariprasath.elango@gmail.com>
On Wed, 14 Mar 2018 18:15:04 +0530
<hariprasath.elango@gmail.com> wrote:
> From: HariPrasath Elango <hariprasath.elango@gmail.com>
>
> Remove the unwated brace and corrected the code block alignment
> accordingly
Changes done in this patch are already taken care. Today, Greg has
applied the patch which had these changes. This patch can be ignore from
the patchset.
Regards,
Ajay
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-14 14:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 12:44 [PATCH 0/7] Cleanup patches for wilc1000 driver hariprasath.elango
2018-03-14 12:44 ` hariprasath.elango
2018-03-14 12:44 ` [PATCH 1/7] staging: wilc1000: Fix code block alignment hariprasath.elango
2018-03-14 12:44 ` hariprasath.elango
2018-03-14 12:45 ` [PATCH 2/7] staging: wilc1000: Destroy mutex object in deinitialization hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-14 12:45 ` [PATCH 3/7] staging: wilc1000: use kmemdup instead of kmalloc and memcpy hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-14 12:45 ` [PATCH 4/7] staging: wilc1000: destroy initialized mutex object hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-14 12:45 ` [PATCH 5/7] staging: wilc1000: replace switch statement by simple if condition hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-19 18:45 ` Greg KH
2018-03-20 6:12 ` <Hariprasath Elango>
2018-03-20 6:12 ` <Hariprasath Elango>
2018-03-20 11:29 ` Dan Carpenter
2018-03-20 11:29 ` Dan Carpenter
2018-03-20 11:42 ` <Hariprasath Elango>
2018-03-20 11:42 ` <Hariprasath Elango>
2018-03-14 12:45 ` [PATCH 6/7] staging: wilc1000: remove unwanted braces and correct code alignment hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-14 14:08 ` Ajay Singh [this message]
2018-03-14 14:08 ` Ajay Singh
2018-03-14 12:45 ` [PATCH 7/7] staging: wilc1000: use kmemdup to replace kmalloc/memcpy hariprasath.elango
2018-03-14 12:45 ` hariprasath.elango
2018-03-16 10:18 ` kbuild test robot
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=20180314193803.39bdd142@ajaysk-VirtualBox \
--to=ajay.kathat@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=hariprasath.elango@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 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.