Messages in this thread | | | Date | Fri, 20 Aug 2021 16:41:42 -0600 | From | Alex Williamson <> | Subject | Re: [PATCH 1/2] s390/vfio-ap: r/w lock for PQAP interception handler function pointer |
| |
On Fri, 20 Aug 2021 18:05:08 -0400 Tony Krowiak <akrowiak@linux.ibm.com> wrote:
> On 8/19/21 1:58 PM, Jason Gunthorpe wrote: > > On Thu, Aug 19, 2021 at 11:54:33AM -0600, Alex Williamson wrote: > > > >> Nope. The only requests for merges through my tree that I'm aware of > >> were [1] and what I understand was the evolution of that here now [2]. > >> Maybe you're thinking of [3], which I do see in mainline where this was > >> 2/2 in that series but afaict only patch 1/2 was committed. I guess > >> that explains why there was no respin based on comments for this patch. > >> Thanks, > > Tony, > > > > If you take Alex's tree from here: > > > > https://github.com/awilliam/linux-vfio/commits/next > > I navigated to this URL and clicked the green 'Code' > button. I was given the option to download the zip file or > use git to checkout the code at the URL displayed > 'https://github.com/awilliam/linux-vfio.git'. I cloned the > repo at that URL and the code was definitely not in any > way similar to my code base. In particular, the > arch/s390/include/asm/kvm_host.h file did not have any > of the crypto structures. > > I then downloaded the zip file and expanded it. The code > looked legitimate, but this was not a git repository, so I > had no way to cherry-pick my patches nor format patches > to post to this mailing list. > > Next, I tried cloning from > 'https://github.com/awilliam/linux-vfio-next.git', > but I was prompted for uid/pw. > > 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.
You can use git fetch to download the objects, ex:
$ git fetch git://github.com/awilliam/linux-vfio.git next $ git checkout FETCH_HEAD
Or you could add a remote, ex:
$ git remote add vfio git://github.com/awilliam/linux-vfio.git $ git remote update vfio $ git checkout vfio/next
The former might be easier and add a lot less crufty objects to your local tree if this is a one-off activity. Thanks,
Alex
| |