From: <kazuhiro3.hayashi@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Cc: <nobuhiro1.iwamatsu@toshiba.co.jp>, <pavel@denx.de>,
<biju.das.jz@bp.renesas.com>, <yuki.saito@toshiba.co.jp>
Subject: RE: [cip-dev] [PATCH 1/1] clk: Fix best_parent_rate after moving code into a separate function
Date: Thu, 1 Feb 2024 04:51:34 +0000 [thread overview]
Message-ID: <TYCPR01MB11385B41C163D5989EF569BBEE1432@TYCPR01MB11385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <ZbosLzzxqI4FyNpq@duo.ucw.cz>
Hello Pavel,
> Is there something wrong with the time here?
Thanks for pointing this out.
Yes, the time in my environment was wrong due to recent setting changes...
Let me resend the patch just in case.
Best regards,
Kazu
> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Pavel Machek
> Sent: Wednesday, January 31, 2024 8:17 PM
> To: hayashi kazuhiro(林 和宏 ＤＭＥ ○ＤＩＧ□ＭＰＳ○ＭＰ４) <kazuhiro3.hayashi@toshiba.co.jp>
> Cc: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 ○ＤＩＴＣ□ＤＩＴ○ＯＳＴ)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; pavel@denx.de; biju.das.jz@bp.renesas.com; saito yuki(齊藤 優貴 ＤＭＥ ○Ｄ
> ＩＧ□ＥＡＳ○ＥＡ３) <yuki.saito@toshiba.co.jp>
> Subject: Re: [cip-dev] [PATCH 1/1] clk: Fix best_parent_rate after moving code into a separate function
>
> Hi!
>
> Is there something wrong with the time here?
>
> Date: Wed, 31 Jan 2024 22:56:04 +0900
> From: Kazuhiro Hayashi <kazuhiro3.hayashi@toshiba.co.jp>
> On Wed 2024-01-31 22:56:04, Kazuhiro Hayashi wrote:
>
> pavel@duo:~$ date
> Wed 31 Jan 2024 12:15:57 PM CET
>
> This will "fix" itself in two hours, but I wonder what went wrong
> there.
>
> Best regards,
> Pavel
> --
> DENX Software Engineering GmbH, Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2024-02-01 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 13:56 [PATCH 0/1] clk: Fix for restructuring for no reparent case Kazuhiro Hayashi
2024-01-31 11:12 ` Pavel Machek
2024-02-01 4:12 ` nobuhiro1.iwamatsu
2024-02-01 9:50 ` Pavel Machek
2024-01-31 13:56 ` [PATCH 1/1] clk: Fix best_parent_rate after moving code into a separate function Kazuhiro Hayashi
2024-01-31 11:17 ` Pavel Machek
2024-02-01 4:51 ` kazuhiro3.hayashi [this message]
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=TYCPR01MB11385B41C163D5989EF569BBEE1432@TYCPR01MB11385.jpnprd01.prod.outlook.com \
--to=kazuhiro3.hayashi@toshiba.co.jp \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=yuki.saito@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.