All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
	Dave Airlie <airlied@redhat.com>,
	linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, kbuild@01.org
Subject: Re: [patch 1/2 -next] dma-buf: double unlock in debugfs code
Date: Thu, 11 Apr 2013 19:40:57 +0000	[thread overview]
Message-ID: <20130411194057.GA7193@kroah.com> (raw)
In-Reply-To: <20130411062339.GA7603@elgon.mountain>

On Thu, Apr 11, 2013 at 09:23:39AM +0300, Dan Carpenter wrote:
> We unlock here when we failed to take the lock.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> This is in linux-next, and I think the debugfs code is only in Sumit's
> tree.

Yes, it's not in mine, so I can't take this, sorry.  Sumit, please apply
this:

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Sumit Semwal <sumit.semwal@linaro.org>,
	Dave Airlie <airlied@redhat.com>,
	linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, kbuild@01.org
Subject: Re: [patch 1/2 -next] dma-buf: double unlock in debugfs code
Date: Thu, 11 Apr 2013 12:40:57 -0700	[thread overview]
Message-ID: <20130411194057.GA7193@kroah.com> (raw)
In-Reply-To: <20130411062339.GA7603@elgon.mountain>

On Thu, Apr 11, 2013 at 09:23:39AM +0300, Dan Carpenter wrote:
> We unlock here when we failed to take the lock.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> This is in linux-next, and I think the debugfs code is only in Sumit's
> tree.

Yes, it's not in mine, so I can't take this, sorry.  Sumit, please apply
this:

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  parent reply	other threads:[~2013-04-11 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11  6:23 [patch 1/2 -next] dma-buf: double unlock in debugfs code Dan Carpenter
2013-04-11  6:23 ` Dan Carpenter
2013-04-11  6:27 ` [kbuild] " Dan Carpenter
2013-04-11  6:27   ` Dan Carpenter
2013-04-11 19:40 ` Greg Kroah-Hartman [this message]
2013-04-11 19:40   ` Greg Kroah-Hartman
     [not found] ` <CAO_48GHvAUmVmmZyHiEXzN3nWtTjC9iz-hEo-z3GrR2T-LZ-0w@mail.gmail.com>
2013-04-12  5:59   ` Dan Carpenter
2013-04-12  5:59     ` Dan Carpenter

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=20130411194057.GA7193@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=kbuild@01.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit.semwal@linaro.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 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.