From: Samuel Ortiz <sameo@linux.intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: lauro.venancio@openbossa.org, aloisio.almeida@openbossa.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFC: nfcwilink: Drop a useless static qualifier
Date: Tue, 20 Oct 2015 06:50:49 +0200 [thread overview]
Message-ID: <20151020045049.GF9764@zurbaran.home> (raw)
In-Reply-To: <1444717864-7109-1-git-send-email-christophe.jaillet@wanadoo.fr>
Hi Christophe,
On Tue, Oct 13, 2015 at 08:31:04AM +0200, Christophe JAILLET wrote:
> There is no need to have the 'struct nfcwilink *drv' variable static in the
> probe function.
> It only wastes a few bytes of memory.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/nfc/nfcwilink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks a lot.
Cheers,
Samuel.
prev parent reply other threads:[~2015-10-20 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 6:31 [PATCH] NFC: nfcwilink: Drop a useless static qualifier Christophe JAILLET
2015-10-20 4:50 ` Samuel Ortiz [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=20151020045049.GF9764@zurbaran.home \
--to=sameo@linux.intel.com \
--cc=aloisio.almeida@openbossa.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=lauro.venancio@openbossa.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox