From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Documentation/process/embargoed-hardware-issues patches for 5.4-rc1
Date: Sun, 29 Sep 2019 12:53:47 +0200 [thread overview]
Message-ID: <20190929105347.GA1949165@kroah.com> (raw)
The following changes since commit f74c2bb98776e2de508f4d607cd519873065118e:
Linux 5.3-rc8 (2019-09-08 13:33:15 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.4-rc1
for you to fetch changes up to dc925a36060e8cef050a9d05c64dae1c30dc5027:
Documentation/process: Clarify disclosure rules (2019-09-29 12:43:18 +0200)
----------------------------------------------------------------
Documentation/process update for 5.4-rc1
Here are 2 small Documentation/process/embargoed-hardware-issues.rst
file updates that missed my previous char/misc pull request for 5.4-rc1.
The first one adds an Intel representative for the process, and the
second one cleans up the text a bit more when it comes to how the
disclosure rules work, as it was a bit confusing to some companies.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Thomas Gleixner (1):
Documentation/process: Clarify disclosure rules
Tony Luck (1):
Documentation/process: Volunteer as the ambassador for Intel
.../process/embargoed-hardware-issues.rst | 42 +++++++++++++++++-----
1 file changed, 34 insertions(+), 8 deletions(-)
next reply other threads:[~2019-09-29 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 10:53 Greg KH [this message]
2019-09-30 3:05 ` [GIT PULL] Documentation/process/embargoed-hardware-issues patches for 5.4-rc1 pr-tracker-bot
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=20190929105347.GA1949165@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox