qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Warner Losh <imp@bsdimp.com>
Cc: Kyle Evans <kevans@freebsd.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/5] bsd-user: minor cleanup patches
Date: Tue, 4 May 2021 17:04:46 +0100	[thread overview]
Message-ID: <CAFEAcA9P-i+gaWLXvxMLouHbC82hWnHU+J4HyG00uTALqb=s-A@mail.gmail.com> (raw)
In-Reply-To: <20210430172746.99818-1-imp@bsdimp.com>

On Fri, 30 Apr 2021 at 18:46, Warner Losh <imp@bsdimp.com> wrote:
>
> The following changes since commit ffa090bc56e73e287a63261e70ac02c0970be61a:
>
>   target/s390x: fix s390_probe_access to check PAGE_WRITE_ORG for writeability (2021-04-23 14:10:56 +0100)
>
> are available in the Git repository at:
>
>   https://gitlab.com/bsdimp/qemu.git tags/pull-bsd-user-20210430
>
> for you to fetch changes up to 58b3beb483d08066548d84eccd007b9d8bd24a2b:
>
>   bsd-user: style tweak: Put {} around all if/else/for statements (2021-04-30 09:14:06 -0600)
>
> ----------------------------------------------------------------
> bsd-user: start to cleanup the mess
>
> A number of small cleanups to get started. All the checkpatch.pl warnings for
> bsdload.c have been fixed, as well as a warning from qemu.h (though more remain
> and this patch series fails the format check still). I've also fixed a
> compile-time warning about a missing break.
>
> ----------------------------------------------------------------
> Warner Losh (5):
>       bsd-user: whitespace changes
>       bsd-user: style tweak: keyword space (
>       bsd-user: style tweak: return is not a function, eliminate ()
>       bsd-user: put back a break; that had gone missing...
>       bsd-user: style tweak: Put {} around all if/else/for statements


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/6.1
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2021-05-04 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 17:27 [PULL 0/5] bsd-user: minor cleanup patches Warner Losh
2021-04-30 17:27 ` [PULL 1/5] bsd-user: whitespace changes Warner Losh
2021-04-30 17:27 ` [PULL 2/5] bsd-user: style tweak: keyword space ( Warner Losh
2021-04-30 17:27 ` [PULL 3/5] bsd-user: style tweak: return is not a function, eliminate () Warner Losh
2021-04-30 17:27 ` [PULL 4/5] bsd-user: put back a break; that had gone missing Warner Losh
2021-04-30 17:27 ` [PULL 5/5] bsd-user: style tweak: Put {} around all if/else/for statements Warner Losh
2021-05-04 16:04 ` Peter Maydell [this message]

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='CAFEAcA9P-i+gaWLXvxMLouHbC82hWnHU+J4HyG00uTALqb=s-A@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --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 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).