From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "greg@enjellic.com" <greg@enjellic.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: XEN 4.1.3 blktap2 patches.
Date: Thu, 20 Sep 2012 21:43:10 +0300 [thread overview]
Message-ID: <20120920184310.GD8912@reaktio.net> (raw)
In-Reply-To: <20120906131834.GV8912@reaktio.net>
On Thu, Sep 06, 2012 at 04:18:34PM +0300, Pasi Kärkkäinen wrote:
> Hello,
>
> On Wed, Aug 29, 2012 at 08:54:28AM +0100, Ian Campbell wrote:
> > On Tue, 2012-08-28 at 13:25 +0100, Dr. Greg Wettstein wrote:
> > > Good morning, hope the day is going well for everyone.
> > >
> > > The patches to fix the blktap2 issues which result in orphaned
> > > tapdisk2 processes and the transitory deadlock on guest shutdown
> > > didn't make it into the 4.1.3 release. Updated patches to address
> > > these problems are available at the following location:
> > >
> > > ftp://ftp.enjellic.com/pub/xen/xen-4.1.3.blktap1.patch
> > > ftp://ftp.enjellic.com/pub/xen/xen-4.1.3.blktap2.patch
> > >
> > > The patches are designed to be applied in order and have been verified
> > > to work against the 4.1.3 release.
> >
> > Please can you post these patches as emails with a changelog and a
> > signed-off-by. You should also CC Ian Jackson since he is the one who
> > does the tools backports.
> >
>
> Added Ian Jackson to CC list..
>
Ping?
Do we need a repost here or can these go into 4.1-testing.hg ?
I see xen-4.1-testing.hg has received other backports now.
-- Pasi
>
> > The changelog should be clear about the backport status. IIRC one of
> > these is a backport from unstable (so the changelog should say of which
> > commit and preserve the original S-o-b) and the other is a
> > reimplementation since too much has changed in unstable so there is no
> > plausible backport (and the changelog should mention this).
> >
> > Ideally these mails would be threaded with subjects "[PATCH 1/2] ..."
> > and "[PATCH 2/2] ..." so that it is obvious that there is a sequence to
> > them. A tool such as hg email will do this for you.
> > http://wiki.xen.org/wiki/Submitting_Xen_Patches has some hints on how to
> > use it.
> >
> > If nothing has changed since the previous posting it may be sufficient
> > to reply to that previous postings with a "ping" message and CC Ian
> > there.
> >
>
> So is repost needed here?
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-09-20 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 12:25 XEN 4.1.3 blktap2 patches Dr. Greg Wettstein
2012-08-28 17:16 ` Pasi Kärkkäinen
2012-08-29 7:54 ` Ian Campbell
2012-09-06 13:18 ` Pasi Kärkkäinen
2012-09-20 18:43 ` Pasi Kärkkäinen [this message]
2012-09-25 11:35 ` Pasi Kärkkäinen
2012-11-05 12:26 ` Pasi Kärkkäinen
-- strict thread matches above, loose matches on Subject: below --
2012-09-02 15:47 Dr. Greg Wettstein
2012-11-07 2:17 Dr. Greg Wettstein
2012-11-07 8:45 ` Pasi Kärkkäinen
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=20120920184310.GD8912@reaktio.net \
--to=pasik@iki.fi \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=greg@enjellic.com \
--cc=xen-devel@lists.xen.org \
/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).