From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nadav Amit <namit@vmware.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Francois Rigault <rigault.francois@gmail.com>,
Jorgen Hansen <jhansen@vmware.com>,
Adit Ranadive <aditr@vmware.com>,
Alexios Zavras <alexios.zavras@intel.com>,
Vishnu Dasa <vdasa@vmware.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] VMCI: Release resource if the work is already queued
Date: Sun, 8 Sep 2019 11:19:44 +0100 [thread overview]
Message-ID: <20190908101944.GA16596@kroah.com> (raw)
In-Reply-To: <00CA348F-5ACC-4A17-A5F6-9B36C92A95E7@vmware.com>
On Sun, Sep 08, 2019 at 04:04:39AM +0000, Nadav Amit wrote:
> > On Sep 7, 2019, at 9:47 PM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Aug 20, 2019 at 01:26:38PM -0700, Nadav Amit wrote:
> >> Francois reported that VMware balloon gets stuck after a balloon reset,
> >> when the VMCI doorbell is removed. A similar error can occur when the
> >> balloon driver is removed with the following splat:
> >
> > <snip>
> >
> > Note, google thinks your email is spam as you are not sending this from
> > a valid vmware.com email server. Please fix this up if you want to make
> > sure your patches actually make it through...
>
> I used gmail servers since I get complaints (mainly from Linus) that our
> email servers use DMARC, and this causes mailing list postings to be
> rejected.
Well the email servers might not reject it now, but gmail itself sure
does as you are lying about what your domain is :(
> I will check again if our open source people got to a solution, or I
> would just send it using my gmail identity, while keeping the vmware
> authorship.
Please do, this is not a viable workflow.
thanks,
greg k-h
prev parent reply other threads:[~2019-09-08 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 20:26 [PATCH] VMCI: Release resource if the work is already queued Nadav Amit
2019-08-22 6:35 ` Vishnu Dasa
2019-09-07 18:47 ` Greg Kroah-Hartman
2019-09-08 4:04 ` Nadav Amit
2019-09-08 10:19 ` Greg Kroah-Hartman [this message]
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=20190908101944.GA16596@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aditr@vmware.com \
--cc=alexios.zavras@intel.com \
--cc=arnd@arndb.de \
--cc=jhansen@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namit@vmware.com \
--cc=rigault.francois@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vdasa@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox