mirror of https://lore.kernel.org/lkml/
 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] rtase: Fix kernel test robot issue
Date: Tue, 15 Apr 2025 03:57:17 +0000	[thread overview]
Message-ID: <4ae769fc0f9f4c26a26f3fb2233ee025@realtek.com> (raw)
In-Reply-To: <3d5a5a7d-a8fb-4a6a-9f3d-3ea27f9d06e7@lunn.ch>

> On Mon, Apr 14, 2025 at 05:36:45PM +0800, Justin Lai wrote:
> > 1. Fix the compile error reported by the kernel test robot by modifying
> > the condition used to detect overflow in rtase_calc_time_mitigation.
> > 2. Fix the compile warning reported by the kernel test robot by
> > increasing the size of ivec->name.
> > 3. Fix a type error in min_t.
> 
> Looks like three patches should be used, not one. You can then include
> the details of what the test robot reported making it easier to
> understand each fix.
> 
> 
>     Andrew
> 
> ---
> pw-bot: cr

Hi Andrew,

Thank you for your response. I will split this patch into three
separate patches and include the detailed report from the kernel
test robot.

Thanks,
Justin

      reply	other threads:[~2025-04-15  3:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-14  9:36 Justin Lai
2025-04-14 12:24 ` Andrew Lunn
2025-04-15  3:57   ` Justin Lai [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=4ae769fc0f9f4c26a26f3fb2233ee025@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
all inboxes | Powered by JetHome®