linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: core: Fix circular locking dependency
Date: Sat, 14 May 2016 10:24:25 -0700	[thread overview]
Message-ID: <57375F49.2020300@roeck-us.net> (raw)
In-Reply-To: <57375B5B.8040809@roeck-us.net>

On 05/14/2016 10:07 AM, Guenter Roeck wrote:
> Hi Wim,
>
> On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
>> Hi Guenter,
>>
>>> lockdep reports the following circular locking dependency.
>>>
>
> You are faster than me this time. I was just about to send you a pull request.
> Sorry for being late. The watchdog-next branch in my repository on kernel.org
> has all patches in my queue, in case you want to have a look.
>
> I'll rebase my branch to yours and see if anything is missing, then send
> you a pull request on top of it if needed.
>

All there. Looks like you picked it up right after I updated the branch
this morning.

>>
>> This patch has been added to linux-watchdog-next.
>>
>
> This patch should probably be tagged for v4.6.
>
Turns out it has a Fixes: tag, so an additional tag should not be necessary.

Thanks,
Guenter

  reply	other threads:[~2016-05-14 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 14:38 [PATCH] watchdog: core: Fix circular locking dependency Guenter Roeck
2016-04-21 14:50 ` One Thousand Gnomes
2016-04-21 23:30   ` Guenter Roeck
2016-05-09 13:53 ` Clemens Gruber
2016-05-09 14:18   ` Guenter Roeck
2016-05-14 16:41 ` Wim Van Sebroeck
2016-05-14 17:07   ` Guenter Roeck
2016-05-14 17:24     ` Guenter Roeck [this message]
2016-05-14 18:29       ` Wim Van Sebroeck

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=57375F49.2020300@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=clemens.gruber@pqgruber.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@iguana.be \
    /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;
as well as URLs for NNTP newsgroup(s).