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] [day] [month] [year] [list]
Message-ID: <OSBPR01MB4773E81EFDC20F555DC0CB70BA799@OSBPR01MB4773.jpnprd01.prod.outlook.com>
Date:   Sat, 3 Apr 2021 22:06:43 +0000
From:   Min Li <min.li.xe@...esas.com>
To:     Greg KH <gregkh@...uxfoundation.org>
CC:     "derek.kiernan@...inx.com" <derek.kiernan@...inx.com>,
        "dragan.cvetic@...inx.com" <dragan.cvetic@...inx.com>,
        "arnd@...db.de" <arnd@...db.de>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH next 2/2] misc: Add Renesas Synchronization Management
 Unit (SMU) support


> 
> Then the patches are independant and they should be sent as such,
> otherwise it causes confusion and our tools get messed up when trying to
> grab the whole "series" of patches.
> 
> Can you please fix this up and just send two independant patches?
> 

Hi Greg

These 2 patches are not independent. Patch 2/2 depends on patch 1/2 to build and work successfully.
They just belong to different domain, patch 1/2 belongs to MFD while patch 2/2 belongs to MISC.
That is why I wasn't sure if I should send both patches to you in the first place. Anyways, I just sent both patches again.

Thanks

Min

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ