From: Samuel Kvasnica <bugreports@list.ims.co.at>
To: "Jan Beulich" <JBeulich@novell.com>, "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: vscsi 2TB patches
Date: Tue, 4 Jan 2011 15:46:43 +0100 [thread overview]
Message-ID: <4D2332D3.3010105@list.ims.co.at> (raw)
In-Reply-To: <4D233968020000780002A36E@vpn.id2.novell.com>
Hi Pasi,
we had some discussion with Jan in the background:
On 01/04/2011 03:14 PM, Jan Beulich wrote:
>>>> On 04.01.11 at 14:34, Samuel Kvasnica <bugreports@list.ims.co.at> wrote:
>>> Did you *try* whether it applies to the 2.6.18 tree? And in order
>>> for it to be applied (given that the 2.6.18 tree is legacy and not
>>> fully maintained anymore), you'd also have to specifically indicate
>>> that it's intended for that tree in the subject, otherwise Keir will
>>> just ignore any Linux patches, assuming they're destined for
>>> pv-ops.
>> well, never tried 2.6.18 and I did not even assume xen community still
>> sticks to 2.6.18 tree
>> for whatever strange reasons. There is no way to even boot 2.6.18 in my
>> case, so lets forget
>> about it, not going to submit patch without testing it on real system.
> In all reality that's what happens quite frequently.
Pasi: do you see a possibility to try it out on 2.6.18 ? I'm not sure
if anybody from Fujitsu takes
actively care, it is quite old code.
>> Well, ok, so now whats the procedure to get this by default at least to
>> opensuse kernel ?
> If it is reasonably applicable to the 2.6.18 kernel, we prefer getting
> it through that tree. Second choice would be to get it through the
> pv-ops one, pointing us to the relevant commits. Third choice (we
> actually did so only very few times thus far, and we're going to be
> reluctant to take anything that could go through either of the
> earlier paths) is to give us the patch on top of our HEAD/master
> tree, accompanied by sufficient information on what the change
> does and how was tested (so we can judge how likely regressions
> from the patch might be).
Jan: but if I understood Pasi, he claims there are no pvscsi drivers
included in the pv-ops tree at all
because it was not ported so far.
But your opensuse pv-ops kernel definitely includes pvscsi drivers -
does this part exist only in
suse kernel tree ?
Sam
next prev parent reply other threads:[~2011-01-04 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 20:11 vscsi 2TB patches Samuel Kvasnica
2011-01-03 23:06 ` Pasi Kärkkäinen
2011-01-04 11:24 ` Samuel Kvasnica
2011-01-04 11:44 ` Jan Beulich
[not found] ` <4D231A46.2000209@list.ims.co.at>
[not found] ` <4D232ADB020000780002A33B@vpn.id2.novell.com>
[not found] ` <4D2321DE.9030706@list.ims.co.at>
[not found] ` <4D233968020000780002A36E@vpn.id2.novell.com>
2011-01-04 14:46 ` Samuel Kvasnica [this message]
2011-01-04 14:55 ` Jan Beulich
2011-01-04 11:47 ` Jan Beulich
2011-01-04 13:03 ` Samuel Kvasnica
2011-01-04 13:07 ` Jan Beulich
2011-01-04 13:23 ` Samuel Kvasnica
2011-01-04 14:06 ` Jan Beulich
2011-01-11 16:26 ` Jan Beulich
2011-01-18 11:45 ` Jan Beulich
2011-01-24 12:24 ` Samuel Kvasnica
2011-01-04 9:47 ` Jan Beulich
2011-01-04 12:57 ` Samuel Kvasnica
2011-01-04 13:01 ` Jan Beulich
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=4D2332D3.3010105@list.ims.co.at \
--to=bugreports@list.ims.co.at \
--cc=JBeulich@novell.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 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.