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: <20210820223049.GJ1721383@nvidia.com>
Date:   Fri, 20 Aug 2021 19:30:49 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Tony Krowiak <akrowiak@...ux.ibm.com>
Cc:     Alex Williamson <alex.williamson@...hat.com>,
        Christian Borntraeger <borntraeger@...ibm.com>,
        linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
        cohuck@...hat.com, pasic@...ux.vnet.ibm.com, jjherne@...ux.ibm.com,
        kwankhede@...dia.com, david@...hat.com
Subject: Re: [PATCH 1/2] s390/vfio-ap: r/w lock for PQAP interception handler
 function pointer

On Fri, Aug 20, 2021 at 06:05:08PM -0400, Tony Krowiak wrote:

> So, the question is, how to I get the linux-vfio-next repo upon which I
> can rebase my patches? I apologize for my ignorance.

Get yourself a kernel git tree somehow, eg by cloning one you already
have

Then something like

$ git fetch https://github.com/awilliam/linux-vfio.git next
$ git reset --hard FETCH_HEAD

Will sort it out, though there are many other varients such as adding
a remote/etc.

When you cloned it from github git checked out the wrong branch for
you - 'git reset --hard origin/next' would fix it too.

Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ