public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: Milan Dadok <milan@dadok.name>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH] 1/4 staging: hv: fix oops in vmbus - udev events
Date: Wed, 28 Oct 2009 15:58:41 -0700	[thread overview]
Message-ID: <20091028225841.GA15420@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C5620E7EE9FF@TK5EX14MBXC114.redmond.corp.microsoft.com>

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

This is seriously annoying, and is something that the lkml mailing list
operators have said they will start blocking soon.  Please remember it.

On Wed, Oct 28, 2009 at 10:48:06PM +0000, Hank Janssen wrote:
> 
> Milan,
> 
> First of all thanks for these patches!
> 
> Greg, I do have a request though. But I am not sure what the right
> approach is. This Patch removes more than I would like. It takes out a
> few things that I would like to Keep in because I need them for prior
> versions of the kernel that we also have this Running on.

I don't understand, what in this patch is needed for older kernels?
This patch only fixes a bug that was preventing uevents from being sent
to userspace.

Also, we don't support older kernel versions in the in-kernel version of
the code, that just does not make any sense, and is why all of that old
stuff was ripped out.

> What is the suggested approach in this case. Can I submit a patch
> instead of this one That keeps some of these items still in?

Sure, what does the patch look like?

thanks,

greg k-h

      reply	other threads:[~2009-10-28 23:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 22:23 [PATCH] 1/4 staging: hv: fix oops in vmbus - udev events Milan Dadok
2009-10-28 22:48 ` Hank Janssen
2009-10-28 22:58   ` Greg KH [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=20091028225841.GA15420@suse.de \
    --to=gregkh@suse.de \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milan@dadok.name \
    /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