From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Maarten ter Huurne <maarten@treewalker.org>
Cc: Felipe Balbi <balbi@ti.com>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: musb: Avoid null pointer dereference in debug logging
Date: Mon, 19 Aug 2013 02:06:44 +0400 [thread overview]
Message-ID: <52114574.3060701@cogentembedded.com> (raw)
In-Reply-To: <1376842864-27839-1-git-send-email-maarten@treewalker.org>
Hello.
On 18-08-2013 20:21, Maarten ter Huurne wrote:
> Since commit 511f3c53 usb_gadget_remove_driver will pass NULL for the
Please also specify that commit's summary line in parens.
> driver argument.
> Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
> ---
> drivers/usb/musb/musb_gadget.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
WBR, Sergei
next prev parent reply other threads:[~2013-08-18 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 16:21 [PATCH] USB: musb: Avoid null pointer dereference in debug logging Maarten ter Huurne
2013-08-18 22:06 ` Sergei Shtylyov [this message]
2013-08-19 6:24 ` Maarten ter Huurne
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=52114574.3060701@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maarten@treewalker.org \
--cc=stern@rowland.harvard.edu \
/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).