On Fri, Jan 05, 2018 at 12:55:41PM -0300, Philippe Mathieu-Daudé wrote:
> Hi Stefan,
>
> On 01/05/2018 12:31 PM, Stefan Hajnoczi wrote:
> > On Wed, Jan 03, 2018 at 06:49:25PM -0300, Philippe Mathieu-Daudé wrote:
> >> +static const char *machines[PROTO_COUNT] = {
> >> + [PROTO_SD] = "nuri",
> >> + //[PROTO_MMC] = "vexpress-a9",
> >> + //[PROTO_SPI] = "lm3s6965evb"
> >> +};
> >> +
> >> +static const uint64_t sizes[] = {
> >> + //512 * M_BYTE,
> >> + //1 * G_BYTE,
> >> + 4 * G_BYTE,
> >> + //64 * G_BYTE,
> >> +};
> >
> > Why are these commented out?
>
> As I didn't feel good feedback for the previous Python qtests, I
> prefered to send this as RFC and to see if this was the good way to go
> before spending more time learning QDECREF() and friends :)
>
> However I again forgot to replace RFC -> NOTFORMERGE in the subject :(
>
> These parameters are commented out because the current sd.c code doesn't
> work with those cases :(
> So to show the qtests is useful and pass Travis/Patchew build, they are
> commented, and to show the current model is broken (until I succeed to
> fix it), one can uncomment these and see failing tests :)If you want to commit commented out code then please include a comment that explains why it's commented out. That way readers understand why it's there. Also please run checkpatch.pl against all patches. It can be run as a commit hook so all your code is checked at commit time: http://blog.vmsplice.net/2011/03/how-to-automatically-run-checkpatchpl.html
signature.asc
Description: PGP signature
