From: Dave Hansen <dave.hansen@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, sashal@kernel.org,
ben@decadent.org.uk, tglx@linutronix.de, labbott@redhat.com,
andrew.cooper3@citrix.com, tsoni@codeaurora.org,
keescook@chromium.org, tony.luck@intel.com,
linux-doc@vger.kernel.org, dan.j.williams@intel.com
Subject: Re: [PATCH 2/4] Documentation/process: describe relaxing disclosing party NDAs
Date: Wed, 11 Sep 2019 09:09:18 -0700 [thread overview]
Message-ID: <5e9f2343-1a76-125a-9555-ab26f15b4487@intel.com> (raw)
In-Reply-To: <20190911154453.GA14152@kroah.com>
On 9/11/19 8:44 AM, Greg KH wrote:
> Intel had months of review time for this document before this was
> published. Your lawyers had it and never objected to this lack of
> inclusion at all, and explictitly said that the document as written was
> fine with them. So I'm sorry, but it is much too late to add something
> like this to the document at this point in time.
Hi Greg,
I'll personally take 100% of the blame for this patch. I intended for
it to show our commitment to work *with* our colleagues in the
community, not to dictate demands. Please consider this as you would
any other patch: a humble suggestion to address what I see as a gap.
Just to be clear: this addition came from me and only me. It did not
come from any Intel lawyers and does not represent any kind of objection
to the process. Intel's support for this process is unconditional and
not dependent on any of these patches.
> Oh, and cute use of the term, "timely manner", as if we are going to
> fall for that one again...
Oh, I think that was actually a quote from an email from Thomas
explaining how he wanted these things dealt with. If you change youer
mind and are open to improvements to this process in the future, I'd be
happy to change this to some kind of explicit deadline if that's preferred.
next prev parent reply other threads:[~2019-09-11 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 17:26 [PATCH 0/4] Documentation/process: embargoed hardware issues additions Dave Hansen
2019-09-10 17:26 ` [PATCH 1/4] Documentation/process: Volunteer as the ambassador for Intel Dave Hansen
2019-09-10 17:26 ` [PATCH 2/4] Documentation/process: describe relaxing disclosing party NDAs Dave Hansen
2019-09-11 10:11 ` Sasha Levin
2019-09-11 14:11 ` Dave Hansen
2019-09-11 15:44 ` Greg KH
2019-09-11 16:09 ` Dave Hansen [this message]
2019-09-25 8:29 ` [PATCH] Documentation/process: Clarify disclosure rules Thomas Gleixner
2019-09-25 15:53 ` Dave Hansen
2019-09-29 10:42 ` [PATCH 2/4] Documentation/process: describe relaxing disclosing party NDAs Greg KH
2019-09-10 17:26 ` [PATCH 3/4] Documentation/process: soften language around conference talk dates Dave Hansen
2019-09-11 15:49 ` Greg KH
2019-09-10 17:26 ` [PATCH 4/4] Documentation/process: add transparency promise to list subscription Dave Hansen
2019-09-11 15:51 ` Greg KH
2019-09-16 8:30 ` Thomas Gleixner
2019-09-11 11:54 ` [PATCH 0/4] Documentation/process: embargoed hardware issues additions 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=5e9f2343-1a76-125a-9555-ab26f15b4487@intel.com \
--to=dave.hansen@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=tsoni@codeaurora.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.