From: Julia Lawall <julia.lawall@lip6.fr>
To: Srishti Sharma <srishtishar@gmail.com>
Cc: lidza.louina@gmail.com, markh@compro.net,
gregkh@linuxfoundation.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 0/2] Remove unused variables in structure definition
Date: Sat, 16 Sep 2017 17:28:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709161728230.1992@hadrien> (raw)
In-Reply-To: <cover.1505572018.git.srishtishar@gmail.com>
On Sat, 16 Sep 2017, Srishti Sharma wrote:
> This patch series attempts to remove unused variables in structure
> variables and the comments associated with them.
Actually, I would say that a structure has fields, not variables.
julia
>
> Srishti Sharma (2):
> Staging: dgnc: Remove unused variables in structure definition
> Staging: dgnc: Remove unused variable in structure
>
> drivers/staging/dgnc/dgnc_driver.h | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> --
> 2.7.4
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/cover.1505572018.git.srishtishar%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>
prev parent reply other threads:[~2017-09-16 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 14:34 Srishti Sharma
2017-09-16 14:35 ` [PATCH 1/2] Staging: dgnc: Remove unused variables in struct dgnc_board Srishti Sharma
2017-09-16 14:35 ` [PATCH 2/2] Staging: dgnc: Remove unused variable in struct channel_t Srishti Sharma
2017-09-16 15:28 ` Julia Lawall [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=alpine.DEB.2.20.1709161728230.1992@hadrien \
--to=julia.lawall@lip6.fr \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=outreachy-kernel@googlegroups.com \
--cc=srishtishar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®