All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Corey Minyard <minyard@acm.org>
Cc: Anton Lundin <glance@acc.umu.se>,
	openipmi-developer@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Openipmi-developer] Issue with panic handling and ipmi
Date: Wed, 27 Oct 2021 13:59:09 -0400	[thread overview]
Message-ID: <YXmTbYhFvDJ0m5KX@sashalap> (raw)
In-Reply-To: <20210920144146.GD545073@minyard.net>

On Mon, Sep 20, 2021 at 09:41:46AM -0500, Corey Minyard wrote:
>On Mon, Sep 20, 2021 at 04:12:31PM +0200, Anton Lundin wrote:
>> On 20 September, 2021 - Corey Minyard wrote:
>>
>> > Well, that was dumb.  Fix follows...
>> >
>> > Thanks for working on this.  On your approval, I'll send this to Linus.
>>
>> Winner winner chicken dinner!
>>
>> This fixes the issue, and now panic timer works, and we get crashdumps
>> to pstore.
>>
>> Great job, I approve!
>>
>>
>> Thanks for your help getting this fixed.
>
>Thanks for reporting this.  I'll get the patch in.

Hey Corey,

Just checking in to see if this patch was lost; I haven't seen it in
Linus's tree just yet.

-- 
Thanks,
Sasha

  reply	other threads:[~2021-10-27 17:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210916145300.GD108031@montezuma.acc.umu.se>
2021-09-16 16:39 ` Issue with panic handling and ipmi Corey Minyard
2021-09-17 10:14   ` Anton Lundin
2021-09-17 12:07     ` Corey Minyard
2021-09-17 12:55       ` Anton Lundin
2021-09-17 13:19         ` [Openipmi-developer] " Corey Minyard
2021-09-17 13:26           ` Anton Lundin
2021-09-20 11:38             ` Corey Minyard
2021-09-20 14:12               ` Anton Lundin
2021-09-20 14:41                 ` Corey Minyard
2021-10-27 17:59                   ` Sasha Levin [this message]
2021-10-27 18:20                     ` Corey Minyard
2021-10-28  1:39                       ` Sasha Levin

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=YXmTbYhFvDJ0m5KX@sashalap \
    --to=sashal@kernel.org \
    --cc=glance@acc.umu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    /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.