From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, mathieu.poirier@linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH] coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute
Date: Tue, 13 Aug 2019 20:37:55 +0200 [thread overview]
Message-ID: <20190813183755.GD6582@kroah.com> (raw)
In-Reply-To: <20190812135328.30952-1-suzuki.poulose@arm.com>
On Mon, Aug 12, 2019 at 02:53:28PM +0100, Suzuki K Poulose wrote:
> commit 5511c0c309db4c526a6e9f8b2b8a1483771574bc upstream
>
> While running the linux-next with CONFIG_DEBUG_LOCKS_ALLOC enabled,
> I get the following splat.
>
Thanks for the backport, now queued up.
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: stable@vger.kernel.org, mathieu.poirier@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute
Date: Tue, 13 Aug 2019 20:37:55 +0200 [thread overview]
Message-ID: <20190813183755.GD6582@kroah.com> (raw)
In-Reply-To: <20190812135328.30952-1-suzuki.poulose@arm.com>
On Mon, Aug 12, 2019 at 02:53:28PM +0100, Suzuki K Poulose wrote:
> commit 5511c0c309db4c526a6e9f8b2b8a1483771574bc upstream
>
> While running the linux-next with CONFIG_DEBUG_LOCKS_ALLOC enabled,
> I get the following splat.
>
Thanks for the backport, now queued up.
greg k-h
next prev parent reply other threads:[~2019-08-13 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 13:53 [PATCH] coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute Suzuki K Poulose
2019-08-12 13:53 ` Suzuki K Poulose
2019-08-13 18:37 ` Greg KH [this message]
2019-08-13 18:37 ` Greg KH
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=20190813183755.GD6582@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.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.