From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using correct index
Date: Wed, 4 Aug 2010 11:23:18 -0700 [thread overview]
Message-ID: <20100804182318.GB29046@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56223FE8EF5@TK5EX14MBXC114.redmond.corp.microsoft.com>
On Wed, Aug 04, 2010 at 05:17:21PM +0000, Hank Janssen wrote:
>
> >And then Greg spoke:
> >> And then Greg spoke:
> > >>>On Tue, Aug 03, 2010 at 05:31:51PM +0000, Hank Janssen wrote:
> > >>> From: Hank Janssen <hjanssen@microsoft.com>
> > >>>
> > >> >Fixed bounce offset kmap problem by using correct index
> > >>
>
> SNIP
>
> > > I actually goofed up in my previous code and used an incorrect index
> > > number For this part of the code. It should have shown up in more
> > > situations than what I have seen oddly enough.
> >
> >Please provide this type of information in the changelog section.
> >
> >If you want something backported to older stable kernels, add a:
> > Cc: stable <stable@kernel.org>
>
> I will re-submit all 5 patches and CC the stable mailing list on it as well.
5? I see 6 of them here :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-08-04 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 17:31 [PATCH 1/6] staging: hv: Fixed bounce kmap problem by using correct index Hank Janssen
2010-08-03 17:37 ` Greg KH
2010-08-04 4:35 ` Hank Janssen
2010-08-04 17:04 ` Greg KH
2010-08-04 17:17 ` Hank Janssen
2010-08-04 18:23 ` Greg KH [this message]
2010-08-04 18:50 ` Hank Janssen
2010-08-04 19:28 ` Greg KH
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=20100804182318.GB29046@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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