xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Enzo Lombardi <enzinol@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: applying ATI patches
Date: Wed, 8 Feb 2012 11:21:43 -0800	[thread overview]
Message-ID: <CACi2erDY4d9OqvTBpFmUAyr_dG5-Fii6pnZeznE5p29-qUACwQ@mail.gmail.com> (raw)
In-Reply-To: <20120208071135.GU12984@reaktio.net>


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

Thank you.
On a related topic: any idea on when/if these patches are going to make it
in the main release branch?
-e

On Tue, Feb 7, 2012 at 11:11 PM, Pasi Kärkkäinen <pasik@iki.fi> wrote:

> On Tue, Feb 07, 2012 at 05:44:29PM -0800, Enzo Lombardi wrote:
> >    Greetings,
> >    I am trying to apply this patch
> >    ( [1]
> http://old-list-archives.xen.org/archives/html/xen-devel/2010-10/msg00284.html) to
> >    the 4.1.2 release code.
> >    If I download the code from the main page
> >    ( [2]http://xen.org/products/xen_source.html ) I see the relevant
> files
> >    but when I enlist through mercurials the files are not there.
> >    Is the patch referring to deprecated/dead code?
> >    Has anybody successfully applied the same patch in the 4.x branch?
>
> If you're talking about qemu-dm files, you first need to build the source
> once,
> so the qemu-xen tree gets fetched (and built) from internet.
>
> -- Pasi
>
>

[-- Attachment #1.2: Type: text/html, Size: 1555 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:[~2012-02-08 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  1:44 applying ATI patches Enzo Lombardi
2012-02-08  7:11 ` Pasi Kärkkäinen
2012-02-08 19:21   ` Enzo Lombardi [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=CACi2erDY4d9OqvTBpFmUAyr_dG5-Fii6pnZeznE5p29-qUACwQ@mail.gmail.com \
    --to=enzinol@gmail.com \
    --cc=pasik@iki.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).