From: Greg KH <gregkh@suse.de>
To: Nicolas Palix <npalix@diku.dk>
Cc: hjanssen@microsoft.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: hv: Replace typedef SG_BUFFER_LIST by struct
Date: Thu, 30 Jul 2009 15:58:44 +0000 [thread overview]
Message-ID: <20090730155844.GB20557@suse.de> (raw)
In-Reply-To: <200907301737.23849.npalix@diku.dk>
On Thu, Jul 30, 2009 at 05:37:23PM +0200, Nicolas Palix wrote:
>
> typedef SG_BUFFER_LIST is removed and its uses are replaced by the use of
> struct scatterlist.
Sweet! thanks for doing this, very nice job, I'll go queue it up.
Hank, you are testing the linux-next tree to make sure we haven't broken
anything yet, right? :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-30 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 15:37 [PATCH] Staging: hv: Replace typedef SG_BUFFER_LIST by struct scatterlist Nicolas Palix
2009-07-30 15:58 ` Greg KH [this message]
2009-07-30 16:14 ` [PATCH] Staging: hv: Replace typedef SG_BUFFER_LIST by struct Hank Janssen
2009-07-30 16:20 ` Greg KH
2009-07-30 18:35 ` Nicolas Palix
2009-07-30 18:37 ` Hank Janssen
2009-07-30 19:52 ` Greg KH
2009-07-30 20:48 ` Nicolas Palix
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=20090730155844.GB20557@suse.de \
--to=gregkh@suse.de \
--cc=hjanssen@microsoft.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npalix@diku.dk \
/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