netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Lai <justinlai0215@realtek.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"horms@kernel.org" <horms@kernel.org>,
	Ping-Ke Shih <pkshih@realtek.com>,
	Larry Chiu <larry.chiu@realtek.com>,
	kernel test robot <lkp@intel.com>
Subject: RE: [PATCH net v2 1/3] rtase: Fix the compile error reported by the kernel test robot
Date: Thu, 17 Apr 2025 05:46:11 +0000	[thread overview]
Message-ID: <ae94b522ec23485e88f8a01a3e09c57c@realtek.com> (raw)
In-Reply-To: <152c9566-a1bd-4082-9f66-6bbe8ab1eb47@lunn.ch>

> 
> On Wed, Apr 16, 2025 at 08:45:32PM +0800, Justin Lai wrote:
> > Fix the following compile error reported by the kernel test robot by
> > modifying the condition used to detect overflow in
> > rtase_calc_time_mitigation.
> 
> The Subject: line is not very useful. It is better to talk about what you are fixing,
> not that a robot reported an issue.
> 
>     Andrew
> 
> ---
> pw-bot: cr

Hi Andrew,

Thank you for your response. I will modify the subject and post a new
version.

Thanks,
Justin

  reply	other threads:[~2025-04-17  5:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 12:45 [PATCH net v2 0/3] Fix kernel test robot issue and type error in min_t Justin Lai
2025-04-16 12:45 ` [PATCH net v2 1/3] rtase: Fix the compile error reported by the kernel test robot Justin Lai
2025-04-16 14:16   ` Andrew Lunn
2025-04-17  5:46     ` Justin Lai [this message]
2025-04-16 12:45 ` [PATCH net v2 2/3] rtase: Fix the compile warning " Justin Lai
2025-04-16 12:45 ` [PATCH net v2 3/3] rtase: Fix a type error in min_t Justin Lai
2025-04-16 14:17   ` Andrew Lunn
2025-04-27 10:46   ` David Laight
2025-04-29  8:39     ` Justin Lai

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=ae94b522ec23485e88f8a01a3e09c57c@realtek.com \
    --to=justinlai0215@realtek.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=larry.chiu@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pkshih@realtek.com \
    /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;
as well as URLs for NNTP newsgroup(s).