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: <eade11f9-22a2-1e7b-93da-d52b63cf9a5f@intel.com>
Date:   Tue, 14 Feb 2023 17:47:16 +0100
From:   "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>
To:     Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>
CC:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the driver-core tree


On 2/14/2023 7:46 AM, Greg KH wrote:
> On Tue, Feb 14, 2023 at 12:57:00PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the pm tree as a different commit (but
>> the same patch):
>>
>>    a0bc3f78d0ff ("kernel/power/energy_model.c: fix memory leak with using debugfs_lookup()")
>>
>> This is commit
>>
>>    a0e8c13ccd6a ("PM: EM: fix memory leak with using debugfs_lookup()")
>>
>> in the pm tree.
> That will be fine, thanks for the warning.

I can drop the EM change, though, if you are going to carry it.

Cheers!


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ