[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1301221103250.20374@pobox.suse.cz>
Date: Tue, 22 Jan 2013 11:04:54 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Fernando Luis Vazquez Cao <fernando_b1@....ntt.co.jp>
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 Tue, 22 Jan 2013, Fernando Luis Vazquez Cao wrote:
> > > 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.
Yes, that's necessary in case you are cherry-picking a commit already
present in Linus' tree that doesn't have explicit "Cc:
stable@...r.kernel.org". Otherwise, -stable tree maintainer is
automatically picking up commits that appear in Linus tree with this tag.
>
> > 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.
It's not strictly necessary. I get copied on them when they are queued in
-stable queue anyway.
> 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.
Ok, thanks.
--
Jiri Kosina
SUSE Labs
--
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/
Powered by blists - more mailing lists