All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Chen <zenghuchen@google.com>
To: lkp@intel.com
Cc: alexandre.belloni@bootlin.com, jesussanp@google.com,
	 linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	 markslevinsky@google.com, oe-kbuild-all@lists.linux.dev,
	 zenghuchen@google.com
Subject: Re: Re: [PATCH] i3c: update dw-i3c-master i3c_clk_cfg function
Date: Tue, 14 Feb 2023 16:24:29 -0500	[thread overview]
Message-ID: <20230214212429.1157315-1-zenghuchen@google.com> (raw)
In-Reply-To: <202302141029.2CS1z9de-lkp@intel.com>

Thanks Intel kernel test robot. This patch was meant for i3c tree.
And I have submitted a new V2 patch which replaced max with max_t to do the type cast.

WARNING: multiple messages have this Message-ID (diff)
From: Jack Chen <zenghuchen@google.com>
To: lkp@intel.com
Cc: alexandre.belloni@bootlin.com, jesussanp@google.com,
	 linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	 markslevinsky@google.com, oe-kbuild-all@lists.linux.dev,
	 zenghuchen@google.com
Subject: Re: Re: [PATCH] i3c: update dw-i3c-master i3c_clk_cfg function
Date: Tue, 14 Feb 2023 16:24:29 -0500	[thread overview]
Message-ID: <20230214212429.1157315-1-zenghuchen@google.com> (raw)
In-Reply-To: <202302141029.2CS1z9de-lkp@intel.com>

Thanks Intel kernel test robot. This patch was meant for i3c tree.
And I have submitted a new V2 patch which replaced max with max_t to do the type cast.

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  parent reply	other threads:[~2023-02-14 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 14:23 [PATCH] i3c: update dw-i3c-master i3c_clk_cfg function Jack Chen
2023-02-13 14:23 ` Jack Chen
2023-02-13 20:17 ` kernel test robot
2023-02-13 20:17   ` kernel test robot
2023-02-14  2:11 ` kernel test robot
2023-02-14  2:11   ` kernel test robot
2023-02-14 20:23   ` Jack Chen
2023-02-14 20:23     ` Jack Chen
2023-02-14 21:24   ` Jack Chen [this message]
2023-02-14 21:24     ` Jack Chen

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=20230214212429.1157315-1-zenghuchen@google.com \
    --to=zenghuchen@google.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=jesussanp@google.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=markslevinsky@google.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.