linux-kernel - Re: [3.13.y-ckt][PATCH 0/1][Hyper-V] Add support for VMBus panic notifier handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55808BF4.4010606@canonical.com>
Date:	Tue, 16 Jun 2015 16:49:56 -0400
From:	Joseph Salisbury <joseph.salisbury@...onical.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	kamal.mostafa@...onical.com, nmeier@...rosoft.com,
	fengguang.wu@...el.com, kys@...rosoft.com, haiyangz@...rosoft.com,
	devel@...uxdriverproject.org, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Subject: Re: [3.13.y-ckt][PATCH 0/1][Hyper-V] Add support for VMBus panic
 notifier handler

On 06/16/2015 04:41 PM, Greg KH wrote:
> On Tue, Jun 16, 2015 at 04:10:46PM -0400, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider including upstream commits 96c1d0581d00f7abe033350edb021a9d947d8d81 and
>> 5ef5b6927f14f29cacd78fa1fb861661a5367f13 in the next v3.13.y-ckt release.  They were
>> included mainline as of v4.1-rc1.  They have been tested and confirmed to resolve
>> http://bugs.launchpad.net/bugs/1463584 .
> Multiple messages sent with the same message-id, yet different subjects
> and content.  That's a sure way to have your messages dropped into a
> spam folder...
>
> Please fix your way of submitting these and resend properly.
>
> thanks,
>
> greg k-h

Thanks for the feedback.  I'll fix things up and resend for all the
stable kernels.

Thanks,

Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/