From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: vscsi 2TB patches Date: Tue, 04 Jan 2011 11:44:55 +0000 Message-ID: <4D231647020000780002A2EE@vpn.id2.novell.com> References: <4D222D71.9020508@list.ims.co.at><20110103230621.GP2754@reaktio.net> <4D230357.3070604@list.ims.co.at> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <4D230357.3070604@list.ims.co.at> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Kvasnica Cc: kama@jp.fujitsu.com, t.horikoshi@jp.fujitsu.com, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> On 04.01.11 at 12:24, Samuel Kvasnica = wrote: >> applied to linux-2.6.18-xen tree. > Huh ??? 2.6.18 ? I remember that was ~5 years ago, cannot imagine even > boot it up > on current hardware. But as long as scsi constant names did not change, = the > patch should be compatible, there is nothing kernel-specific. But you need to specify what xenbits tree you intend this to be applied to, and there you have the choice between 2.6.18, XCI/XCP, and (not really on xenbits) pv-ops. Since the forward porting of the 2.6.18 tree doesn't generally leave the files in drivers/xen/scsi*/ completely untouched, it cannot be taken as given that the patch you used on top of .31/.34 will apply as-is on .18. Jan