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: <ho6fq5f6dd3bj25kidhsnwlqj2xgd5rmjkh7t33lmaqclh3a5f@5udgwp4nvsfe>
Date:   Tue, 23 May 2023 14:59:04 -0700
From:   Davidlohr Bueso <dave@...olabs.net>
To:     Dan Williams <dan.j.williams@...el.com>
Cc:     dave.jiang@...el.com, alison.schofield@...el.com,
        vishal.l.verma@...el.com, ira.weiny@...el.com,
        Jonathan.Cameron@...wei.com, fan.ni@...sung.com,
        a.manzanares@...sung.com, linux-cxl@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] cxl: Handle background commands

On Tue, 23 May 2023, Dan Williams wrote:

>Like Linus I want to see the conflicts. Whenever possible base on latest
>Linus tag like v6.4-rc3.

So I'm clear, do you want me to resend this series based on -rc3?

Frankly I'm always confused as to what is the correct/preferred branch to
do development on.

>In this case I will add this to a
>for-6.5/cxl-background topic branch based on 'fixes' for now, but once
>'fixes' hits v6.4-rc4 I will move the topic baseline just to have it not
>be based on a random point in the history.

Ok, thanks for picking this up.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ