linux-kernel - Re: [git pull] Input updates for v6.10-rc5

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: <Znm5EzNHCk_g4puh@google.com>
Date: Mon, 24 Jun 2024 11:21:07 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [git pull] Input updates for v6.10-rc5

On Mon, Jun 24, 2024 at 02:10:49PM -0400, Linus Torvalds wrote:
> On Mon, 24 Jun 2024 at 11:59, Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> >
> > Ugh, I was on a wrong branch ('next' for the next merge window) when I
> > created the tag. I'll fix my script, but in the meantime should I:
> >
> > - blow away the bad tag and re-create under the same name as before
> >   (input-for-v6.10-rc5) or
> >
> > - blow away the bad tag and use new name for the correct one (somthing
> >   like input-for-v6.10-rc5-fixed)?
> 
> Either works. Some people just re-use the same tag name, others will
> always use new names. I don't personally worry about it, and whatever
> you feel better about works for me.

OK, great. I re-created the tag using the original name but tagging the
right commit.

Please pull from:

git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.10-rc5

It should resolve to 7c7b1be19b22 ("Input: ads7846 - use spi_device_id
table").

Thanks!

-- 
Dmitry