From: mpagano@gentoo.org (Mike Pagano )
To: Gentoo Kernel List <gentoo-kernel@lists.gentoo.org>
Subject: [gentoo-kernel] [ANNOUNCE] genpatches-4.20-11 release
Date: Wed, 20 Feb 2019 12:09:48 +0000 (UTC) [thread overview]
Message-ID: <20190220120949.A7B92335CE9@smtp.gentoo.org> (raw)
This is an automated email announcing the release of genpatches-4.20-11
CHANGES SINCE 4.20-10
-----------------------
proj/linux-patches: Patch not compatible with 4.20 (Mike Pagano)
D 5011_enable-cpu-optimizations-for-gcc8.patch
proj/linux-patches: Linux patch 4.20.11 (Mike Pagano)
A 1010_linux-4.20.11.patch
proj/linux-patches: cpu optimization patch for gcc >= 8 (Mike Pagano)
A 5011_enable-cpu-optimizations-for-gcc8.patch
proj/linux-patches: Rename patch for clarity (Mike Pagano)
R100 5010_enable-additional-cpu-optimizations-for-gcc.patch 5010_enable-additional-cpu-optimizations-for-gcc-4.9.patch
ABOUT GENPATCHES
----------------
genpatches is the patchset applied to some kernels available in Portage.
For more information, see the genpatches homepage:
http://dev.gentoo.org/~mpagano/genpatches
For a simple example of how to use genpatches in your kernel ebuild, look at a
recent gentoo-sources ebuild.
reply other threads:[~2019-02-20 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190220120949.A7B92335CE9@smtp.gentoo.org \
--to=mpagano@gentoo.org \
--cc=gentoo-kernel@lists.gentoo.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