From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: mvtwsi: fix hang on SPL bind
Date: Thu, 11 Apr 2019 08:01:31 -0400 [thread overview]
Message-ID: <20190411120131.GY4664@bill-the-cat> (raw)
In-Reply-To: <4ba44032-6d27-28e5-9c33-1e1c62728110@denx.de>
On Thu, Apr 11, 2019 at 11:49:44AM +0200, Heiko Schocher wrote:
> Hello Stefan,
>
> Am 11.04.2019 um 11:31 schrieb Stefan Roese:
> >Hi Heiko,
> >
> >On 10.04.19 07:38, Heiko Schocher wrote:
> >>Hello Baruch,
> >>
> >>Am 07.04.2019 um 11:30 schrieb Baruch Siach:
> >>>The mvebu specific debug register is not accessible when the bind code
> >>>runs in SPL. Skip it.
> >>>
> >>>Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> >>>---
> >>> drivers/i2c/mvtwsi.c | 4 ++++
> >>> 1 file changed, 4 insertions(+)
> >>
> >>Applied to u-boot-i2c.git master
> >
> >Could you please hold this patch a bit longer. I'm not 100% sure, if
> >this is the correct fix. Please see this thread for more details.
> >
> >https://lists.denx.de/pipermail/u-boot/2019-April/364818.html
>
> Oh, wasn;t aware of this ... Hmm.. pull request is already send
> to Tom ... but Tom hasn;t merged it ...
>
> @Tom: Should I remove this patch from u-boot-i2c.git and send a new
> pull request or should we revert this commit, if a better solution
> is found?
Please re-send your PR, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190411/84f17b71/attachment.sig>
next prev parent reply other threads:[~2019-04-11 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 9:30 [U-Boot] [PATCH] i2c: mvtwsi: fix hang on SPL bind Baruch Siach
2019-04-09 15:18 ` Stefan Roese
2019-04-09 17:40 ` Baruch Siach
2019-04-10 5:38 ` Heiko Schocher
2019-04-11 9:31 ` Stefan Roese
2019-04-11 9:49 ` Heiko Schocher
2019-04-11 12:01 ` Tom Rini [this message]
2019-04-11 13:27 ` Heiko Schocher
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=20190411120131.GY4664@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