From: Kalle Valo <kvalo@codeaurora.org>
To: Bas Peters <baspeters93@gmail.com>
Cc: Bas Peters <baspeters93@gmail.com>,
linville@tuxdriver.com, johannes.berg@intel.com, dcbw@redhat.com,
libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: libertas: remove unnecessary check before calling debugfs_remove
Date: Fri, 27 Feb 2015 08:07:20 +0000 (UTC) [thread overview]
Message-ID: <20150227080720.BA59C13FA62@smtp.codeaurora.org> (raw)
In-Reply-To: <1423643586-11002-1-git-send-email-baspeters93@gmail.com>
> Debugfs_remove will check for error or NULL for us, so it is not
> necessary to do this here.
>
> Signed-off-by: Bas Peters <baspeters93@gmail.com>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
prev parent reply other threads:[~2015-02-27 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 8:33 [PATCH] net: wireless: libertas: debugfs.c: remove unnecessary check before calling debugfs_remove Bas Peters
2015-02-27 8:07 ` Kalle Valo [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=20150227080720.BA59C13FA62@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=baspeters93@gmail.com \
--cc=dcbw@redhat.com \
--cc=johannes.berg@intel.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).