All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	David Vrabel <david.vrabel@citrix.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
	mrushton@amazon.com, msw@amazon.com, boris.ostrovsky@oracle.com
Subject: Re: [Xen-devel] [GIT PULL] (xen) stable/for-jens-3.14 : NFO: trying to register non-static key. the code is fine but needs lockdep annotation.
Date: Tue, 11 Feb 2014 14:44:42 -0700	[thread overview]
Message-ID: <52FA99CA.8070505@kernel.dk> (raw)
In-Reply-To: <1009282985.20140211212157@eikelenboom.it>

On 2014-02-11 13:21, Sander Eikelenboom wrote:
>
> Tuesday, February 11, 2014, 7:21:56 PM, you wrote:
>
>> On 11/02/14 18:15, Roger Pau Monné wrote:
>>> On 11/02/14 18:52, David Vrabel wrote:
>>>>
>>> That would mean that unmap_purged_grants would no longer be static and
>>> I should also add a prototype for it in blkback/common.h, which is kind
>>> of ugly IMHO.
>
>> But less ugly than initializing work with a NULL function, IMO.
>
>>> commit 980e72e45454b64ccb7f23b6794a769384e51038
>>> Author: Roger Pau Monne <roger.pau@citrix.com>
>>> Date:   Tue Feb 11 19:04:06 2014 +0100
>>>
>>>      xen-blkback: init persistent_purge_work work_struct
>>>
>>>      Initialize persistent_purge_work work_struct on xen_blkif_alloc (and
>>>      remove the previous initialization done in purge_persistent_gnt). This
>>>      prevents flush_work from complaining even if purge_persistent_gnt has
>>>      not been used.
>>>
>>>      Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>
>> Reviewed-by: David Vrabel <david.vrabel@citrix.com>
>
> And a Tested-by: Sander Eikelenboom <linux@eikelenboom.it>

Konrad, I was going to ship my current tree today, but looks like we 
need this too.

-- 
Jens Axboe

  reply	other threads:[~2014-02-11 21:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 18:44 [GIT PULL] (xen) stable/for-jens-3.14 Konrad Rzeszutek Wilk
2014-02-10 19:54 ` Jens Axboe
2014-02-11 15:52   ` [Xen-devel] [GIT PULL] (xen) stable/for-jens-3.14 : NFO: trying to register non-static key. the code is fine but needs lockdep annotation Sander Eikelenboom
2014-02-11 15:52     ` Sander Eikelenboom
2014-02-11 15:56     ` Konrad Rzeszutek Wilk
2014-02-11 16:07       ` Sander Eikelenboom
2014-02-11 16:07         ` Sander Eikelenboom
2014-02-11 17:40         ` Roger Pau Monné
2014-02-11 17:40           ` Roger Pau Monné
2014-02-11 17:52           ` David Vrabel
2014-02-11 17:52             ` David Vrabel
2014-02-11 18:15             ` Roger Pau Monné
2014-02-11 18:15               ` Roger Pau Monné
2014-02-11 18:21               ` David Vrabel
2014-02-11 18:21                 ` David Vrabel
2014-02-11 20:21                 ` Sander Eikelenboom
2014-02-11 20:21                   ` Sander Eikelenboom
2014-02-11 21:44                   ` Jens Axboe [this message]
2014-02-12  3:14                     ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-02-12  3: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=52FA99CA.8070505@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=mrushton@amazon.com \
    --cc=msw@amazon.com \
    --cc=roger.pau@citrix.com \
    --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.