Message ID | 1396940651-10513-1-git-send-email-mjt@msgid.tls.msk.ru |
---|---|
State | New |
Headers | show |
Thanks, and I will/should finish the left trivial patches within this week (2014-04-13) On 04/08/2014 03:04 PM, Michael Tokarev wrote: > From: Chen Gang <gang.chen.5i5j@gmail.com> > > When you ask for an accelerator not supported for your target, you get > a bogus "accelerator does not exist" message: > > $ qemu-system-arm -machine none,accel=kvm > KVM not supported for this target > "kvm" accelerator does not exist. > No accelerator found! > > Suppress it. > > Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com> > Reviewed-by: Markus Armbruster <armbru@redhat.com> > Signed-off-by: Michael Tokarev <mjt@tls.msk.ru> > --- > vl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/vl.c b/vl.c > index 9975e5a..db9ea90 100644 > --- a/vl.c > +++ b/vl.c > @@ -2740,7 +2740,7 @@ static int configure_accelerator(QEMUMachine *machine) > if (!accel_list[i].available()) { > printf("%s not supported for this target\n", > accel_list[i].name); > - continue; > + break; > } > *(accel_list[i].allowed) = true; > ret = accel_list[i].init(machine); >
On 8 April 2014 08:04, Michael Tokarev <mjt@tls.msk.ru> wrote: > And there's a series of 3 patches by Peter Maydell which adds casts > to uint* in a few places. Those are also quite simple and safe, even > with quite some disagreement about whenever this is necessary to > start with -- I mean the int128 change, the other changes are good. > At least this way we make it consistent with other parts of the code. I was not expecting those to go in for 2.0... thanks -- PMM
08.04.2014 12:10, Peter Maydell wrote: > On 8 April 2014 08:04, Michael Tokarev <mjt@tls.msk.ru> wrote: >> And there's a series of 3 patches by Peter Maydell which adds casts >> to uint* in a few places. Those are also quite simple and safe, even >> with quite some disagreement about whenever this is necessary to >> start with -- I mean the int128 change, the other changes are good. >> At least this way we make it consistent with other parts of the code. > > I was not expecting those to go in for 2.0... Well. At least one of them is entirely safe (hw/ide/ahci.c). Another - xbzrle.c - looks okay, and even maybe fixing a bug. And this int128 thing is okay too, except that the whole thing is questionable as has been mentioned in that thread. I can prepare another pull request without xbzrle and int128 changes, or even without ahci change too, but I'm not sure it is worth the effort - I think everything is okay to go. I'll take your word for this. Thanks, /mjt
On 8 April 2014 09:52, Michael Tokarev <mjt@tls.msk.ru> wrote: > Well. At least one of them is entirely safe (hw/ide/ahci.c). > Another - xbzrle.c - looks okay, and even maybe fixing a bug. > And this int128 thing is okay too, except that the whole thing > is questionable as has been mentioned in that thread. > > I can prepare another pull request without xbzrle and int128 changes, > or even without ahci change too, but I'm not sure it is worth the > effort - I think everything is okay to go. I'll take your word for this. Well, anything that goes in today is going to get at best two days of being tested before the release. To me that argues fairly strongly for not putting anything in unless it is fixing a genuine bug. thanks -- PMM
Peter Maydell <peter.maydell@linaro.org> writes: > On 8 April 2014 09:52, Michael Tokarev <mjt@tls.msk.ru> wrote: >> Well. At least one of them is entirely safe (hw/ide/ahci.c). >> Another - xbzrle.c - looks okay, and even maybe fixing a bug. >> And this int128 thing is okay too, except that the whole thing >> is questionable as has been mentioned in that thread. >> >> I can prepare another pull request without xbzrle and int128 changes, >> or even without ahci change too, but I'm not sure it is worth the >> effort - I think everything is okay to go. I'll take your word for this. > > Well, anything that goes in today is going to get at best two > days of being tested before the release. To me that argues > fairly strongly for not putting anything in unless it is > fixing a genuine bug. Seconded.
08.04.2014 14:57, Markus Armbruster wrote: > Peter Maydell <peter.maydell@linaro.org> writes: > >> On 8 April 2014 09:52, Michael Tokarev <mjt@tls.msk.ru> wrote: >>> Well. At least one of them is entirely safe (hw/ide/ahci.c). >>> Another - xbzrle.c - looks okay, and even maybe fixing a bug. >>> And this int128 thing is okay too, except that the whole thing >>> is questionable as has been mentioned in that thread. >>> >>> I can prepare another pull request without xbzrle and int128 changes, >>> or even without ahci change too, but I'm not sure it is worth the >>> effort - I think everything is okay to go. I'll take your word for this. >> >> Well, anything that goes in today is going to get at best two >> days of being tested before the release. To me that argues >> fairly strongly for not putting anything in unless it is >> fixing a genuine bug. > > Seconded. -trivial does not fix bugs. Only documentation bugs, which does not met the above definition. So no -trivial patches for 2.0 anymore. Thanks, /mjt