All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Byrne <john.l.byrne@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] Allow blktap to build as a module
Date: Wed, 03 Jan 2007 10:15:42 -0800	[thread overview]
Message-ID: <459BF2CE.3090702@hp.com> (raw)
In-Reply-To: <C1C117DC.6A24%Keir.Fraser@cl.cam.ac.uk>

Keir Fraser wrote:
> IIRC blktap doesn't straightforwardly build and work as a module. Some code
> cleanup is required (getting rid of zap_page_range()?). There's no point in
> taking the trivial Makefile fragment until that is fixed satisfactorily.
> 
>  -- Keir

I thought I'd tested it. (You had me worried) zap_page_range() got 
exported in 12678:260426e3924f as part of the virtual frame buffer patch.

If Jan has a patch that doesn't change the name, that would be better. I 
didn't much like the name change, but I was being lazy.

John

> 
> On 3/1/07 8:12 am, "Jan Beulich" <jbeulich@novell.com> wrote:
> 
>> I had posted a patch for this quite a while back (no clue why it wasn't picked
>> up),
>> though allowing the module to be more logically named blktap.ko. I'd really
>> dislike to
>> now have a blktp.ko. Jan
>>
>>>>> John Byrne <john.l.byrne@hp.com> 03.01.07 01:58 >>>
>> The patch is against xen-unstable 13205:886f7312257e, but should also
>> apply to 3.0.4.
>>
>> Signed-off-by: John Byrne <john.l.byrne@hp.com>
>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> 
> 

      parent reply	other threads:[~2007-01-03 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-03  0:58 [PATCH] Allow blktap to build as a module John Byrne
2007-01-03  8:12 ` Jan Beulich
2007-01-03  8:20   ` Keir Fraser
2007-01-03  8:41     ` Jan Beulich
2007-01-03 12:45       ` Daniel P. Berrange
2007-01-03 18:15     ` John Byrne [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=459BF2CE.3090702@hp.com \
    --to=john.l.byrne@hp.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.