All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/2][PV-on-HVM] Fix compile errors for RHEL/SLES
Date: Mon, 03 Dec 2007 15:23:07 -0500	[thread overview]
Message-ID: <475465AB.3040007@virtualiron.com> (raw)
In-Reply-To: <47546410.6010901@virtualiron.com>


[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]

Please disregard point 3.

I realized this was against a prior patch that we do not feel is ready 
for submission just yet.

The other 2 chunks still apply,

I can re-submit, if necessary.

Ben Guthro wrote:
> [PATCH 1/2][PV-on-HVM] Fix compile errors for RHEL/SLES
> Fix compile errors on a couple of distros.
> 1st fix was for SLES10-SP1 and SLES10-SP2:
> netif_tx_lock_bh was pulled back into older kernels, and thus must be 
> detected.
> 2nd fix was for RHEL4-U5 which pulled back the irqreturn_t feature 
> into an older kernel. This too must be detected.
> 3rd fix was fixing a compile error in a printk for a more strict 
> compile in RHEL4-U5
>
> Signed-off-by: Ben Guthro <bguthro@virtualiron.com>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


[-- Attachment #1.2: Type: text/html, Size: 1525 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      reply	other threads:[~2007-12-03 20:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 20:16 [PATCH 1/2][PV-on-HVM] Fix compile errors for RHEL/SLES Ben Guthro
2007-12-03 20:23 ` Ben Guthro [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=475465AB.3040007@virtualiron.com \
    --to=bguthro@virtualiron.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.