From: Greg KH <gregkh@suse.de>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Hank Janssen <hjanssen@microsoft.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staging: hv: Fix null pointer error after vmbus loading
Date: Thu, 22 Oct 2009 15:56:07 -0700 [thread overview]
Message-ID: <20091022225607.GB11244@suse.de> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF72180B3E1E@TK5EX14MBXC126.redmond.corp.microsoft.com>
On Thu, Oct 22, 2009 at 04:14:31PM +0000, Haiyang Zhang wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
>
> Fix null pointer error after vmbus loading.
I'm not going to accept this patch, please see my previous email as to
why you should not be checking the name at all.
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-22 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 16:14 [PATCH] Staging: hv: Fix null pointer error after vmbus loading Haiyang Zhang
2009-10-22 22:56 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-23 18:14 Haiyang Zhang
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=20091022225607.GB11244@suse.de \
--to=gregkh@suse.de \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@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