mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 于佼良 <yujiaoliang@vivo.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	opensource.kernel <opensource.kernel@vivo.com>
Subject: Re: [PATCH v3] wifi: cfg80211: Use kmemdup_array instead of kmemdup for multiple allocation
Date: Fri, 23 Aug 2024 07:56:47 +0000	[thread overview]
Message-ID: <6cc2a3bf-0444-463f-98d9-daec3f95865d@vivo.com> (raw)
In-Reply-To: <871q2hgi08.fsf@kernel.org>

在 2024/8/22 14:59, Kalle Valo 写道:
> [Some people who received this message don't often get email from kvalo@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Yu Jiaoliang <yujiaoliang@vivo.com> writes:
>
>> Let the kememdup_array() take care about multiplication and possible
>> overflows.
>>
>> ---
>> v2:
>> -Change sizeof(limits[0]) to sizeof(*limits)
>> -Fix title prefix
>>
>> v3:
>> -Fix R-b tag
>> -Leave --- above this information
>>
>> Signed-off-by: Yu Jiaoliang <yujiaoliang@vivo.com>
>> Reviewed-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> Now Signed-off-by and Reviewed-by are in the wrong location. Please
> carefully read the wiki page below how to submit patches.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Hi Kalle,

I have updated the position of the changelog and submitted patch v4. 
Thank you.

Best Regards,

Yu


      reply	other threads:[~2024-08-23  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22  2:42 Yu Jiaoliang
2024-08-22  6:59 ` Kalle Valo
2024-08-23  7:56   ` 于佼良 [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=6cc2a3bf-0444-463f-98d9-daec3f95865d@vivo.com \
    --to=yujiaoliang@vivo.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=opensource.kernel@vivo.com \
    --cc=pabeni@redhat.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®