On Wed, May 9, 2018 at 8:49 AM, Peter Maydell <peter.mayd...@linaro.org> wrote:
> On 8 May 2018 at 21:07, Michael Clark <m...@sifive.com> wrote: > > The following changes since commit c8b7e627b4269a3bc3ae41d9f42054 > 7a47e6d9b9: > > > > Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2018-05-04' > into staging (2018-05-04 14:42:46 +0100) > > > > are available in the git repository at: > > > > https://github.com/riscv/riscv-qemu.git tags/riscv-qemu-2.13-minor- > fixes-2 > > > > for you to fetch changes up to fc28db142ea9331d24d08a6418efa93e258a6876: > > > > riscv: requires libfdt (2018-05-09 07:57:57 +1200) > > > > ---------------------------------------------------------------- > > RISC-V: QEMU 2.13 Minor Fixes > > > > * Require libfdt when configuring for 'riscv*-softmmu' > > * Increase HTIF priority and allow zero base address > > > > Consider backporting to stable branch for 2.12.1 > > Ah, if you want something flagged to be backported to > the stable branch, the way to do that is to include > the line "Cc: qemu-sta...@nongnu.org" in the commit > message. We use the same approach for flagging things > for stable as the Linux kernel. (Individual submaintainers > are generally in the best position to decide whether > something should go into stable, and this system leaves > that choice up to them. A patch submitter can also suggest > something for stable when you submit the initial patch for > review by adding the Cc: line and cc'ing qemu-stable on the > patchmail.) > Okay. Given the 'Cc is missing in the commit (only on the cover) I could send a separate patch. Or I can respin with the 'Cc on the configure libfdt dependency fix commit and remove the backport message from the tag...
