All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>
Subject: [PULL 0/4] Misc patches queues
Date: Tue,  7 Jul 2026 18:50:23 +0100	[thread overview]
Message-ID: <20260707175027.3029620-1-berrange@redhat.com> (raw)

The following changes since commit 94826ec1370328375c3b6d1e80fdc94c8f46c348:

  Merge tag 'accel-20260706' of https://github.com/philmd/qemu into staging (2026-07-06 18:38:14 +0200)

are available in the Git repository at:

  https://gitlab.com/berrange/qemu tags/misc-next-pull-request

for you to fetch changes up to 64d0d2efdd2822c827aa7cd276e15c7cefaccb95:

  docs: outline some guidelines for security classification (2026-07-07 18:36:15 +0100)

----------------------------------------------------------------
* Outline security classification guidelines
* Use QEMU lock guards in inotify code
* Fix certificate error checking

----------------------------------------------------------------

Daniel P. Berrangé (1):
  docs: outline some guidelines for security classification

Evgeny Kolmakov (1):
  util/filemonitor-inotify: Use QEMU_LOCK_GUARD()

Peter Maydell (1):
  io/channel-socket: Document why we can ignore socket_set_cork() errors

yujun (1):
  crypto/x509-utils: fix gnutls error code in crt_init failure path

 crypto/x509-utils.c        |  3 +-
 docs/system/security.rst   | 63 ++++++++++++++++++++++++++++++++++++++
 io/channel-socket.c        |  6 ++++
 util/filemonitor-inotify.c | 28 +++++------------
 4 files changed, 79 insertions(+), 21 deletions(-)

-- 
2.55.0



             reply	other threads:[~2026-07-07 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 17:50 Daniel P. Berrangé [this message]
2026-07-07 17:50 ` [PULL 1/4] crypto/x509-utils: fix gnutls error code in crt_init failure path Daniel P. Berrangé
2026-07-07 17:50 ` [PULL 2/4] util/filemonitor-inotify: Use QEMU_LOCK_GUARD() Daniel P. Berrangé
2026-07-07 17:50 ` [PULL 3/4] io/channel-socket: Document why we can ignore socket_set_cork() errors Daniel P. Berrangé
2026-07-07 17:50 ` [PULL 4/4] docs: outline some guidelines for security classification Daniel P. Berrangé
2026-07-09  5:22   ` Michael S. Tsirkin
2026-07-09  5:52   ` Michael S. Tsirkin
2026-07-09  8:03 ` [PULL 0/4] Misc patches queues Daniel P. Berrangé

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=20260707175027.3029620-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.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.