mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Chris Holvenstot <cholvenstot@comcast.net>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Issue building kernel driver
Date: Thu, 1 Nov 2007 18:51:26 +0100	[thread overview]
Message-ID: <20071101175126.GA7227@stusta.de> (raw)
In-Reply-To: <1193938746.7555.7.camel@localhost>

On Thu, Nov 01, 2007 at 12:39:06PM -0500, Chris Holvenstot wrote:
> 
> Although it may not be popular with the crowd here, I do have a valid
> reason to run Windows - and I accomidate this using the VirtualBox
> product.  
> 
> Since I try to be slightly useful and build as many of the "test" kernel
> images I can I end up rebuilding the VirtualBox kernel driver (open
> source) on an almost daily basis.
>...
> I am not sure if this should be reported to the kernel folks or the
> VirtualBox folks - but the kernel code is what changed.  However I will
> post this on the VirtualBox forum too.

We had a (different) bug report involving exactly this external driver 
at some older post 2.6.23 kernel where it turned out it was a problem in 
this driver - and this one also looks really like a problem in their 
driver.

Generally, problems with external drivers should be reported to the 
vendors of these drivers and not here (unless it's clear it's a bug in 
the kernel and not in the driver).

> Thanks

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-11-01 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 17:39 Chris Holvenstot
2007-11-01 17:51 ` Adrian Bunk [this message]
2007-11-01 18:03   ` Chris Holvenstot
2007-11-01 18:05 ` Sam Ravnborg
2007-11-01 18:12 ` Frans Pop

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=20071101175126.GA7227@stusta.de \
    --to=bunk@kernel.org \
    --cc=cholvenstot@comcast.net \
    --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

all inboxes | Powered by JetHome®