linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [git pull] Input updates for v6.10-rc5
@ 2024-06-23 23:05 Dmitry Torokhov
  2024-06-24 14:28 ` Linus Torvalds
  2024-07-20  0:05 ` pr-tracker-bot
  0 siblings, 2 replies; 7+ messages in thread
From: Dmitry Torokhov @ 2024-06-23 23:05 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel, linux-input

Hi Linus,

Please pull from:

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

to receive updates for the input subsystem. You will get:

- fixes for ili210x and elantech drivers

- new products IDs added to xpad controller driver

- a tweak to i8042 driver to always keep keyboard in Ayaneo Kun
  handheld in raw mode

- populated "id_table" in ads7846 touchscreen driver to make sure
  non-OF instantiated devices can properly determine the model data.

Changelog:
---------

Alexander Stein (1):
      Input: ads7846 - use spi_device_id table

John Keeping (1):
      Input: ili210x - fix ili251x_read_touch_data() return value

Jonathan Denose (1):
      Input: elantech - fix touchpad state on resume for Lenovo N24

Luke D. Jones (1):
      Input: xpad - add support for ASUS ROG RAIKIRI PRO

Tobias Jakobi (1):
      Input: i8042 - add Ayaneo Kun to i8042 quirk table

Diffstat:
--------

 drivers/input/joystick/xpad.c         |  1 +
 drivers/input/mouse/elantech.c        | 31 +++++++++++++++++++++++++++++++
 drivers/input/serio/i8042-acpipnpio.h | 18 ++++++++++++++++--
 drivers/input/touchscreen/ads7846.c   | 12 +++++++++++-
 drivers/input/touchscreen/ili210x.c   |  4 ++--
 5 files changed, 61 insertions(+), 5 deletions(-)

Thanks.


-- 
Dmitry

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [git pull] Input updates for v6.10-rc5
  2024-06-23 23:05 [git pull] Input updates for v6.10-rc5 Dmitry Torokhov
@ 2024-06-24 14:28 ` Linus Torvalds
  2024-06-24 15:59   ` Dmitry Torokhov
  2024-07-20  0:05 ` pr-tracker-bot
  1 sibling, 1 reply; 7+ messages in thread
From: Linus Torvalds @ 2024-06-24 14:28 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-kernel, linux-input

On Sun, 23 Jun 2024 at 19:05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
>
> Please pull from:
>
>         git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.10-rc5
>
> to receive updates for the input subsystem. You will get:

Nope. I get something entirely different. I think you tagged the wrong state.

              Linus

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [git pull] Input updates for v6.10-rc5
  2024-06-24 14:28 ` Linus Torvalds
@ 2024-06-24 15:59   ` Dmitry Torokhov
  2024-06-24 18:10     ` Linus Torvalds
  0 siblings, 1 reply; 7+ messages in thread
From: Dmitry Torokhov @ 2024-06-24 15:59 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel, linux-input

On Mon, Jun 24, 2024 at 10:28:09AM -0400, Linus Torvalds wrote:
> On Sun, 23 Jun 2024 at 19:05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >
> > Please pull from:
> >
> >         git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git tags/input-for-v6.10-rc5
> >
> > to receive updates for the input subsystem. You will get:
> 
> Nope. I get something entirely different. I think you tagged the wrong state.

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)?

I do not want to keep the bad tag to avoid confusion in the future.

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [git pull] Input updates for v6.10-rc5
  2024-06-24 15:59   ` Dmitry Torokhov
@ 2024-06-24 18:10     ` Linus Torvalds
  2024-06-24 18:21       ` Dmitry Torokhov
  0 siblings, 1 reply; 7+ messages in thread
From: Linus Torvalds @ 2024-06-24 18:10 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-kernel, linux-input

On Mon, 24 Jun 2024 at 11:59, Dmitry Torokhov <dmitry.torokhov@gmail.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.

               Linus

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [git pull] Input updates for v6.10-rc5
  2024-06-24 18:10     ` Linus Torvalds
@ 2024-06-24 18:21       ` Dmitry Torokhov
  2024-06-24 18:41         ` pr-tracker-bot
  0 siblings, 1 reply; 7+ messages in thread
From: Dmitry Torokhov @ 2024-06-24 18:21 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: linux-kernel, linux-input

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@gmail.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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: [git pull] Input updates for v6.10-rc5
  2024-06-24 18:21       ` Dmitry Torokhov
@ 2024-06-24 18:41         ` pr-tracker-bot
  0 siblings, 0 replies; 7+ messages in thread
From: pr-tracker-bot @ 2024-06-24 18:41 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: Linus Torvalds, linux-kernel, linux-input

The pull request you sent on Mon, 24 Jun 2024 11:21:07 -0700:

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

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/55027e689933ba2e64f3d245fb1ff185b3e7fc81

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [git pull] Input updates for v6.10-rc5
  2024-06-23 23:05 [git pull] Input updates for v6.10-rc5 Dmitry Torokhov
  2024-06-24 14:28 ` Linus Torvalds
@ 2024-07-20  0:05 ` pr-tracker-bot
  1 sibling, 0 replies; 7+ messages in thread
From: pr-tracker-bot @ 2024-07-20  0:05 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: Linus Torvalds, linux-kernel, linux-input

The pull request you sent on Sun, 23 Jun 2024 16:05:38 -0700:

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

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/866a5c7e2781cf1b019072288f1f5c64186dcb63

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2024-07-20  0:05 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-06-23 23:05 [git pull] Input updates for v6.10-rc5 Dmitry Torokhov
2024-06-24 14:28 ` Linus Torvalds
2024-06-24 15:59   ` Dmitry Torokhov
2024-06-24 18:10     ` Linus Torvalds
2024-06-24 18:21       ` Dmitry Torokhov
2024-06-24 18:41         ` pr-tracker-bot
2024-07-20  0:05 ` pr-tracker-bot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).