lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <PA4PR04MB963855F4620A2E2C48B2DC2CD1802@PA4PR04MB9638.eurprd04.prod.outlook.com>
Date: Thu, 15 Aug 2024 06:20:48 +0000
From: David Lin <yu-hao.lin@....com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kvalo@...nel.org" <kvalo@...nel.org>, "johannes@...solutions.net"
	<johannes@...solutions.net>, "briannorris@...omium.org"
	<briannorris@...omium.org>, "francesco@...cini.it" <francesco@...cini.it>,
	Pete Hsieh <tsung-hsien.hsieh@....com>
Subject: RE: [EXT] Re: [PATCH v2 40/43] wifi: nxpwifi: add wmm.h

Hi Greg,

	So that mean I still need to add description for every file, right?

	Once if confirmed, I will prepare patch v3.

Thanks,
David

> -----Original Message-----
> From: Greg KH <gregkh@...uxfoundation.org>
> Sent: Thursday, August 15, 2024 1:08 PM
> To: David Lin <yu-hao.lin@....com>
> Cc: linux-wireless@...r.kernel.org; linux-kernel@...r.kernel.org;
> kvalo@...nel.org; johannes@...solutions.net; briannorris@...omium.org;
> francesco@...cini.it; Pete Hsieh <tsung-hsien.hsieh@....com>
> Subject: Re: [EXT] Re: [PATCH v2 40/43] wifi: nxpwifi: add wmm.h
> 
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, report the message using the 'Report
> this email' button
> 
> 
> On Thu, Aug 15, 2024 at 01:52:18AM +0000, David Lin wrote:
> > Hi Greg,
> >
> >       Following the guideline for new driver, it should let every file as a
> single patch for review and generate a final
> >       single patch after reviewing. I think stuffs mentioned by you can be
> got from cover letter.
> >
> >       If I misunderstood anything, please let me know.
> 
> Please read the kernel documentation for how to submit kernel changes in a
> way that we can properly review, and accept them.  As-is, there is nothing we
> can do with this series at all, sorry.
> 
> greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ