From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: use invd instead of wbinvd in real mode start code
Date: Mon, 17 Feb 2020 11:02:25 -0500 [thread overview]
Message-ID: <20200217160225.GK18302@bill-the-cat> (raw)
In-Reply-To: <CAHp75VdZs2MKnFOYSdyQjqAQQAngmjB5g4C2uJMW=Vo06UE6ZA@mail.gmail.com>
On Mon, Feb 17, 2020 at 05:33:59PM +0200, Andy Shevchenko wrote:
> On Mon, Feb 17, 2020 at 5:32 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Mon, Feb 17, 2020 at 5:09 PM Wolfgang Denk <wd@denx.de> wrote:
> > > In message <CAHp75VdUY7zJfkc4YV-KTt1aEKg9Ggy6PsJAEOkgo9eCtQx9Kg@mail.gmail.com> you wrote:
> > > >
> > > > > > git bisect is the usual way to figure out the culprit.
> > > > >
> > > > > Too much work to do this way.
> > >
> > > If you find bisecting is too much work you probably still do it
> > > manually. Why don't you use tbot to automize such boring and time
> > > consuming tasks?
> >
> > Bisection time something about 10%, while 90% is flashing the board
> > and, given the result, triggering either bad or good next cycle.
>
> And btw, doing git bisect is not mandatory technique to follow as long
> as I can guarantee the (reproducible) result, right?
No, it's not. But personally 'git bisect run' and 'git stash' are the
two features that put git far above any other SCM I've used.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200217/171a8d55/attachment.sig>
next prev parent reply other threads:[~2020-02-17 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHp75VdtevMO=AWeZZ-kfmo0Dx5RrGBZEW8Mm5ubLU2pm3Nh=g@mail.gmail.com>
2020-02-17 12:31 ` Fwd: use invd instead of wbinvd in real mode start code Andy Shevchenko
2020-02-17 12:33 ` Andy Shevchenko
[not found] ` <CAK7LNASQuuEWCypyK+TDYa1eYk__KKRZ1Z8JgsEbhd+4KNFNjw@mail.gmail.com>
[not found] ` <CAHp75Veri=85osuFy0xDukEKN9zAULJpk+1sTdHynTL_deK=0Q@mail.gmail.com>
2020-02-17 13:47 ` Andy Shevchenko
2020-02-17 13:52 ` Bin Meng
2020-02-17 14:00 ` Andy Shevchenko
2020-02-17 14:49 ` Bin Meng
2020-02-17 15:31 ` Andy Shevchenko
2020-02-17 15:09 ` Wolfgang Denk
2020-02-17 15:13 ` Tom Rini
2020-02-17 15:32 ` Andy Shevchenko
2020-02-17 15:33 ` Andy Shevchenko
2020-02-17 16:02 ` Tom Rini [this message]
2020-02-17 16:04 ` Wolfgang Denk
2020-02-18 5:48 ` Heiko Schocher
2020-02-18 10:45 ` Andy Shevchenko
2020-02-18 11:06 ` Heiko Schocher
2020-02-18 11:29 ` Andy Shevchenko
2020-02-18 14:43 ` Tom Rini
2020-02-18 15:37 ` Andy Shevchenko
2020-02-19 13:14 ` Wolfgang Denk
2020-02-19 13:42 ` Tom Rini
2020-02-19 14:04 ` Heiko Schocher
2020-02-17 16:05 ` Tom Rini
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=20200217160225.GK18302@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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