linux-kernel - Re: [PATCH v2] HID: add support for Sony RF receiver with USB product id 0x0374

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: <50FE2A34.3050607@lab.ntt.co.jp>
Date:	Tue, 22 Jan 2013 14:57:08 +0900
From:	Fernando Luis Vazquez Cao <fernando_b1@....ntt.co.jp>
To:	Jiri Kosina <jkosina@...e.cz>
CC:	linux-input@...r.kernel.org, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Antonio Ospite <ospite@...denti.unina.it>
Subject: Re: [PATCH v2] HID: add support for Sony RF receiver with USB product
 id 0x0374

On Wed, 2013-01-16 at 11:44 +0100, Jiri Kosina wrote:
> On Wed, 16 Jan 2013, Fernando Luis Vazquez Cao wrote:
>
> > I noticed that the patch was tagged "for-3.9". Does this mean
> > that it is too late to get it merged during the current release
> > cycle?
>
> I currently don't have anything queued for 3.8, and this particular patch
> doesn't justify a separate pull request.
>
> Once it's in Linus' tree, it can be easily pushed out to all existing
> -stable branches (including 3.8-stable, once it's created).
>
> If I am gfoing to be sending pull request for 3.8 to Linus still due to
> some important bugfix, I will be including this.

Ok, thank you for the explanation. I really appreciate it.


> > If possible, I would like to get it backported to 3.7-stable (and
> > possibly 3.2 stable), since without it a whole family of Sony desktop
> > computers is unusable under Linux out of the box. Should I do it myself
> > or do you have a process in place for HID stable patches?
>
> If the patch had
>
> 	Cc: stable@...r.kernel.org
>
> in it, it'd be picked for -stable queue automatically.

I considered doing that but I thought and upstream commit
ID was needed.


> Otherwise, anyone is free to take it once it's in Linus' tree and sent
> to to stable@...r.kernel.org for inclusion.


So it is the standard procedure. I just wanted to make
sure whether you wanted to have all the -stable patches
funnelled through you. I will send the patch to -stable
directly and Cc you as soon as it makes it into Linus'
tree.


By the way, I will be replying to this email with a
follow-up patch that I forgot to send the last time
around. It is just documentation for the quirk.

Thanks,
Fernando
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/