All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel@lists.xensource.com, catalin.marinas@arm.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: backport a4dba130891271084344c12537731542ec77cb85 to 3.16+
Date: Tue, 27 Jan 2015 16:10:38 -0800	[thread overview]
Message-ID: <20150128001038.GB17677@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501121704380.3058@kaball.uk.xensource.com>

On Mon, Jan 12, 2015 at 06:09:33PM +0000, Stefano Stabellini wrote:
> Hi all,
> I would like to request a backport of the following commit:
> 
> 
> commit a4dba130891271084344c12537731542ec77cb85
> Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Date:   Fri Nov 21 11:07:39 2014 +0000
> 
>     xen/arm/arm64: introduce xen_arch_need_swiotlb
> 
> 
> to stable trees from 3.16 onward (3.16 included).
> 
> 
> The commit needs to be slightly modified because is_device_dma_coherent
> is not available on kernels < 3.19, so I just removed the call,
> thus assuming that the device is not coherent on arm (slower but safe):

A diff of a diff is hard to apply, please send the reworked patch in a
format that I can apply it in.

thanks,

greg k-h

  parent reply	other threads:[~2015-01-28  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 18:09 backport a4dba130891271084344c12537731542ec77cb85 to 3.16+ Stefano Stabellini
2015-01-12 18:09 ` Stefano Stabellini
2015-01-15 11:04 ` Luis Henriques
2015-01-15 11:04   ` Luis Henriques
2015-01-28  0:10 ` Greg KH [this message]
2015-01-28 12:01   ` Stefano Stabellini
2015-01-28 12:01     ` Stefano Stabellini

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=20150128001038.GB17677@kroah.com \
    --to=greg@kroah.com \
    --cc=catalin.marinas@arm.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stefano.stabellini@eu.citrix.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.