On Fri, 2025-10-24 at 21:24 +0100, Ruben Wauters wrote: > Hello > > I have recently attempted to setup dim to be able to push my patches to > drm-misc-next. > > I have attempted to use my openpgp auth subkey as an ssh key and I > believe I have somewhat succeeded, I managed to setup dim, and have > managed to push my patch to drm-misc-next, however upon dim attempting > to update for-linux-next/for-linux-next-fixes it no longer accepts my > ssh key and asks for username and password. Entering my username and > password appears to fail always, even if my password is correct.
Just an update on this, I seem to have fixed it by using an access token. I am now feeling somewhat silly as this was the obvious solution and there was no need for this message at all. Ruben > This of course causes drm-tip to not be rebuilt as it fails before it > reaches that point. > > It seems someone else has pushed a patch after mine so I beleive the > issue this time has been resolved and for-linux-next and drm-tip seem > to include my commit, however I would ideally like to not have this > issue again, and resolve it. > > If anyone has any ideas I'm open to suggestions > > Thank you > > Ruben Wauters
signature.asc
Description: This is a digitally signed message part
