From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kbuild@01.org, Linaro MM SIG <linaro-mm-sig@lists.linaro.org>,
kernel-janitors@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2 -next] dma-buf: double unlock in debugfs code
Date: Fri, 12 Apr 2013 05:59:32 +0000 [thread overview]
Message-ID: <20130412055931.GI6692@mwanda> (raw)
In-Reply-To: <CAO_48GHvAUmVmmZyHiEXzN3nWtTjC9iz-hEo-z3GrR2T-LZ-0w@mail.gmail.com>
On Fri, Apr 12, 2013 at 08:43:05AM +0530, Sumit Semwal wrote:
> Hi Dan,
>
> On Apr 11, 2013 11:54 AM, "Dan Carpenter" <dan.carpenter@oracle.com> wrote:
> >
> > We unlock here when we failed to take the lock.
> Thanks for catching this; I will add it to the for-next queue.
>
> Could I merge this change with the main patch while submitting to mainline?
> With an attribution to you, of course.
Yeah. Just merge it. Don't stress about attribution.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kbuild@01.org, Linaro MM SIG <linaro-mm-sig@lists.linaro.org>,
kernel-janitors@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2 -next] dma-buf: double unlock in debugfs code
Date: Fri, 12 Apr 2013 08:59:32 +0300 [thread overview]
Message-ID: <20130412055931.GI6692@mwanda> (raw)
In-Reply-To: <CAO_48GHvAUmVmmZyHiEXzN3nWtTjC9iz-hEo-z3GrR2T-LZ-0w@mail.gmail.com>
On Fri, Apr 12, 2013 at 08:43:05AM +0530, Sumit Semwal wrote:
> Hi Dan,
>
> On Apr 11, 2013 11:54 AM, "Dan Carpenter" <dan.carpenter@oracle.com> wrote:
> >
> > We unlock here when we failed to take the lock.
> Thanks for catching this; I will add it to the for-next queue.
>
> Could I merge this change with the main patch while submitting to mainline?
> With an attribution to you, of course.
Yeah. Just merge it. Don't stress about attribution.
regards,
dan carpenter
next prev parent reply other threads:[~2013-04-12 5:59 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
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 [this message]
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=20130412055931.GI6692@mwanda \
--to=dan.carpenter@oracle.com \
--cc=airlied@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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.