xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: George Dunlap <george.dunlap@citrix.com>,
	Paul Durrant <paul@xen.org>,
	"Ian Jackson" <ian.jackson@citrix.com>, Wei Liu <wl@xen.org>
Subject: [PATCH for-4.15 2/7] CHANGELOG.md: xl PCI configuration doc, xenstore MTU entries
Date: Thu, 1 Apr 2021 14:38:22 +0100	[thread overview]
Message-ID: <20210401133827.362216-2-george.dunlap@citrix.com> (raw)
In-Reply-To: <20210401133827.362216-1-george.dunlap@citrix.com>

Signed-off-by: George Dunlap <george.dunlap@citrix.com>
---
CC: Paul Durrant <paul@xen.org>
CC: Ian Jackson <ian.jackson@citrix.com>
CC: Wei Liu <wl@xen.org>
---
 CHANGELOG.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index f7ce6682b9..086a0e50d0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -15,6 +15,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
  - Switched MSR accesses to deny by default policy.
  - Intel Processor Trace support (Tech Preview)
  - Named PCI devices for xl/libxl
+ - Improved documentation for xl PCI configuration format
  - Support for zstd-compressed dom0 (x86) and domU kernels
  - Library improvements from NetBSD ports upstreamed
  - CI loop: Add Alpine Linux, Ubuntu Focal targets; drop CentOS 6
@@ -23,7 +24,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
  - x86: Allow domains to use AVX-VNNI instructions
  - Factored out HVM-specific shadow code, improving code clarity and reducing the size of PV-only hypervisor builds
  - Added XEN_SCRIPT_DIR configuration option to specify location for Xen scripts, rather than hard-coding /etc/xen/scripts
-
+ - xennet: Documented a way for the backend (or toolstack) to specify MTU to the frontend
 
 ### Removed / support downgraded
 
-- 
2.30.2



  reply	other threads:[~2021-04-01 13:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 13:38 [PATCH for-4.15 1/7] CHANGELOG.md: Mention XEN_SCRIPT_DIR George Dunlap
2021-04-01 13:38 ` George Dunlap [this message]
2021-04-01 15:30   ` [PATCH for-4.15 2/7] CHANGELOG.md: xl PCI configuration doc, xenstore MTU entries Paul Durrant
2021-04-01 13:38 ` [PATCH for-4.15 3/7] CHANGELOG.md: Some additional affordances in various xl subcommands George Dunlap
2021-04-01 13:38 ` [PATCH for-4.15 4/7] CHANGELOG.md: Mention various ARM errata George Dunlap
2021-04-01 14:13   ` Jan Beulich
2021-04-01 16:14     ` Julien Grall
2021-04-01 13:38 ` [PATCH for-4.15 5/7] CHANGELOG.md: Various new entries, mostly x86 George Dunlap
2021-04-01 14:13   ` Jan Beulich
2021-04-01 13:38 ` [PATCH for-4.15 6/7] CHANGELOG.md: Various entries, mostly xenstore George Dunlap
2021-04-01 13:54   ` Juergen Gross
2021-04-01 14:00   ` Andrew Cooper
2021-04-01 14:13     ` George Dunlap
2021-04-01 14:16       ` Andrew Cooper
2021-04-01 14:45         ` George Dunlap
2021-04-01 13:38 ` [PATCH for-4.15 7/7] CHANGELOG.md: irq-max-guests George Dunlap
2021-04-01 14:17   ` Jan Beulich
2021-04-01 14:46     ` George Dunlap
2021-04-06 16:31 ` [PATCH for-4.15 1/7] CHANGELOG.md: Mention XEN_SCRIPT_DIR Ian Jackson

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=20210401133827.362216-2-george.dunlap@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=paul@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).