From: Jens Axboe <axboe@fb.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] (xen) for-jens-4.3 for your 'for-4.3/drivers' branch
Date: Wed, 7 Oct 2015 13:53:01 -0600 [thread overview]
Message-ID: <5615781D.4020506@fb.com> (raw)
In-Reply-To: <20151007192623.GB23861@l.oracle.com>
On 10/07/2015 01:26 PM, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
>
> Please git pull an update branch to your 'for-4.3/drivers' branch (which
> oddly I don't see does not have the previous pull?)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.3
>
> which has two fixes - one where we use the Xen blockfront EFI driver and
> don't release all the requests, the other if the allocation of resources
> for a particular state failed - we would go back 'Closing' and assume that
> an structure would be allocated while in fact it may not be - and crash.
>
> Please pull!
>
> P.S.
> The patches also have 'stable@vger.kernel.org' on them.
>
> drivers/block/xen-blkback/xenbus.c | 38 ++++++++++++++++++++------------------
> drivers/block/xen-blkfront.c | 3 ++-
> 2 files changed, 22 insertions(+), 19 deletions(-)
>
> Cathy Avery (1):
> xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing)
>
> Roger Pau Monne (1):
> xen/blkback: free requests on disconnection
There's only one commit in that pull request, the patch from Roger is
already in mainline from the last pull request. I think your mistake is
looking at for-4.3/drivers - this branch is defunct as soon as Linus has
pulled the initial bits for 4.3. After that, for-linus is the branch
that carries fixes for the _current_ branch.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@fb.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: [GIT PULL] (xen) for-jens-4.3 for your 'for-4.3/drivers' branch
Date: Wed, 7 Oct 2015 13:53:01 -0600 [thread overview]
Message-ID: <5615781D.4020506@fb.com> (raw)
In-Reply-To: <20151007192623.GB23861@l.oracle.com>
On 10/07/2015 01:26 PM, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
>
> Please git pull an update branch to your 'for-4.3/drivers' branch (which
> oddly I don't see does not have the previous pull?)
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.3
>
> which has two fixes - one where we use the Xen blockfront EFI driver and
> don't release all the requests, the other if the allocation of resources
> for a particular state failed - we would go back 'Closing' and assume that
> an structure would be allocated while in fact it may not be - and crash.
>
> Please pull!
>
> P.S.
> The patches also have 'stable@vger.kernel.org' on them.
>
> drivers/block/xen-blkback/xenbus.c | 38 ++++++++++++++++++++------------------
> drivers/block/xen-blkfront.c | 3 ++-
> 2 files changed, 22 insertions(+), 19 deletions(-)
>
> Cathy Avery (1):
> xen-blkfront: check for null drvdata in blkback_changed (XenbusStateClosing)
>
> Roger Pau Monne (1):
> xen/blkback: free requests on disconnection
There's only one commit in that pull request, the patch from Roger is
already in mainline from the last pull request. I think your mistake is
looking at for-4.3/drivers - this branch is defunct as soon as Linus has
pulled the initial bits for 4.3. After that, for-linus is the branch
that carries fixes for the _current_ branch.
--
Jens Axboe
next prev parent reply other threads:[~2015-10-07 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 19:26 [GIT PULL] (xen) for-jens-4.3 for your 'for-4.3/drivers' branch Konrad Rzeszutek Wilk
2015-10-07 19:53 ` Jens Axboe [this message]
2015-10-07 19:53 ` Jens Axboe
2015-10-07 20:32 ` Konrad Rzeszutek Wilk
2015-10-07 20:34 ` Jens Axboe
2015-10-07 20:34 ` 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=5615781D.4020506@fb.com \
--to=axboe@fb.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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.