All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, stefanha@redhat.com,
	Daniel Henrique Barboza <danielhb413@gmail.com>
Subject: [PULL 0/1] ppc queue
Date: Thu, 17 Nov 2022 12:16:56 -0300	[thread overview]
Message-ID: <20221117151657.182061-1-danielhb413@gmail.com> (raw)

The following changes since commit 2c8311241d1f7377bb4ff76064b1d1fe15166413:

  Update VERSION for v7.2.0-rc1 (2022-11-15 18:56:38 -0500)

are available in the Git repository at:

  https://gitlab.com/danielhb/qemu.git tags/pull-ppc-20221117

for you to fetch changes up to 049b4ad66984aad278b3fc0a75b5a995c9b66a16:

  target/ppc: Fix build warnings when building with 'disable-tcg' (2022-11-17 11:28:04 -0300)

----------------------------------------------------------------
ppc patch queue for 2022-11-17:

Short queue with a build regression fix when using --disable-tcg.

----------------------------------------------------------------
Vaibhav Jain (1):
      target/ppc: Fix build warnings when building with 'disable-tcg'

 target/ppc/cpu_init.c    | 2 ++
 target/ppc/excp_helper.c | 2 ++
 2 files changed, 4 insertions(+)


             reply	other threads:[~2022-11-17 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 15:16 Daniel Henrique Barboza [this message]
2022-11-17 15:16 ` [PULL 1/1] target/ppc: Fix build warnings when building with 'disable-tcg' Daniel Henrique Barboza
2022-11-17 20:08 ` [PULL 0/1] ppc queue Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2023-04-09 21:23 Cédric Le Goater
2023-04-10 13:28 ` Peter Maydell
2022-11-11 10:05 Daniel Henrique Barboza
2022-11-12  2:32 ` Stefan Hajnoczi
2022-08-04 18:41 Daniel Henrique Barboza
2022-08-04 21:05 ` Richard Henderson
2022-03-28  7:32 Cédric Le Goater
2022-03-28 14:24 ` Peter Maydell
2021-11-29 20:53 Cédric Le Goater
2021-11-30  8:04 ` Richard Henderson

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=20221117151657.182061-1-danielhb413@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanha@redhat.com \
    /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.