From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] (xen) stable/for-jens-3.8
Date: Fri, 15 Feb 2013 08:31:21 -0500 [thread overview]
Message-ID: <20130215133121.GF11777@phenom.dumpdata.com> (raw)
In-Reply-To: <20130215093052.GZ21269@kernel.dk>
On Fri, Feb 15, 2013 at 10:30:52AM +0100, Jens Axboe wrote:
> On Thu, Feb 14 2013, Konrad Rzeszutek Wilk wrote:
> > Hey Jens,
> >
> > Please git pull the following branch:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.8
> >
> > which has fixes to the blkback that I hope you can push to Linus for 3.8.
> > The one that is quite vicious is the "xen-blkfront: drop the use of
> > llist_for_each_entry_safe". It is a fix to re-do an "free-ing" loop - otherwise
> > we hit a GCC 4.1.1 bug (so RHEL5 based) that turns the loop in an unbound one.
>
> Taking pulls this late better all be stable@ worty patches. Are they?
I think that is OK - considering I just sent you _another_ git pull.
If it is not too much trouble, could you take it in your 3.9 tree and once Linus
pulls them I will send an email to Greg asking them to backport the git commits?
Much appreciated and sorry for these very late patches.
>
> --
> Jens Axboe
>
next prev parent reply other threads:[~2013-02-15 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 23:26 [GIT PULL] (xen) stable/for-jens-3.8 Konrad Rzeszutek Wilk
2013-02-15 9:30 ` Jens Axboe
2013-02-15 13:31 ` Konrad Rzeszutek Wilk [this message]
2013-02-15 13:14 ` One more: " Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2012-11-09 14:55 Konrad Rzeszutek Wilk
2012-11-12 16:19 ` Jens Axboe
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=20130215133121.GF11777@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.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