From: Sasha Levin <Alexander.Levin@microsoft.com>
To: "mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tools/lib/lockdep: fixes for v4.19
Date: Thu, 6 Sep 2018 15:30:21 +0000 [thread overview]
Message-ID: <20180906153020.GW16300@sasha-vm> (raw)
In-Reply-To: <20180829000356.GA161312@sasha-vm>
Ping?
On Tue, Aug 28, 2018 at 08:03:56PM -0400, Sasha Levin wrote:
>Ping?
>
>On Mon, Aug 13, 2018 at 07:05:36PM +0000, Sasha Levin wrote:
>>Hi Ingo,
>>
>>Please pull the following minor fixes for liblockdep.
>>
>>Also available at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes
>>
>>Sasha Levin (3):
>> tools/lib/lockdep: update Sasha Levin email to MSFT
>> tools/lib/lockdep: add empty nmi.h
>> tools/lib/lockdep: add dummy task_struct state member
>>
>>MAINTAINERS | 2 +-
>>tools/include/linux/lockdep.h | 3 +++
>>tools/include/linux/nmi.h | 0
>>3 files changed, 4 insertions(+), 1 deletion(-)
>>create mode 100644 tools/include/linux/nmi.h
>>
>>--
>>2.17.1
next prev parent reply other threads:[~2018-09-06 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 19:05 [PATCH 0/3] tools/lib/lockdep: fixes for v4.19 Sasha Levin
2018-08-13 19:05 ` [PATCH 1/3] tools/lib/lockdep: update Sasha Levin email to MSFT Sasha Levin
2018-09-10 12:36 ` [tip:locking/urgent] tools/lib/lockdep: Update " tip-bot for Sasha Levin
2018-08-13 19:05 ` [PATCH 2/3] tools/lib/lockdep: add empty nmi.h Sasha Levin
2018-09-10 12:37 ` [tip:locking/urgent] tools/lib/lockdep: Add " tip-bot for Sasha Levin
2018-08-13 19:05 ` [PATCH 3/3] tools/lib/lockdep: add dummy task_struct state member Sasha Levin
2018-09-10 12:38 ` [tip:locking/urgent] tools/lib/lockdep: Add " tip-bot for Sasha Levin
2018-08-29 0:03 ` [PATCH 0/3] tools/lib/lockdep: fixes for v4.19 Sasha Levin
2018-09-06 15:30 ` Sasha Levin [this message]
2018-09-10 11:49 ` Ingo Molnar
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=20180906153020.GW16300@sasha-vm \
--to=alexander.levin@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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.