From: Ben Hutchings <ben@decadent.org.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
devel@driverdev.osuosl.org,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Torsten Crass <torsten.crass@eBiology.de>,
Jarod Wilson <jarod@redhat.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 3.0.y 0/4] Re: lirc_serial spuriously claims assigned port and irq to be in use
Date: Wed, 7 Mar 2012 21:34:41 +0000 [thread overview]
Message-ID: <20120307213441.GX12704@decadent.org.uk> (raw)
In-Reply-To: <20120307200407.GB26451@kroah.com>
On Wed, Mar 07, 2012 at 12:04:07PM -0800, Greg Kroah-Hartman wrote:
> On Fri, Mar 02, 2012 at 02:39:13PM -0600, Jonathan Nieder wrote:
> > Ben Hutchings wrote:
> > > On Thu, 2012-03-01 at 21:45 -0600, Jonathan Nieder wrote:
> >
> > >> Would some of these patches (e.g., at least patches 1, 2, and 5) be
> > >> appropriate for inclusion in the 3.0.y and 3.2.y stable kernels from
> > >> kernel.org?
> > >
> > > Assuming they haven't caused any regressions, I think everything except
> > > 9b98d6067971 (4/5) would be appropriate.
> >
> > Great. Here are the aforementioned patches rebased against 3.0.y, in
> > the hope that some interested person can confirm they still work. The
> > only backporting needed was to adjust to the lack of
> > drivers/staging/lirc -> drivers/staging/media/lirc renaming.
>
> So they should also go to 3.2-stable, right?
Yes, only for 3.2 a simple cherry-pick should work.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
prev parent reply other threads:[~2012-03-07 21:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 5:49 [PATCH 1/5] staging: lirc_serial: Fix init/exit order Ben Hutchings
2011-11-16 5:52 ` [PATCH 2/5] staging: lirc_serial: Free resources on failure paths of lirc_serial_probe() Ben Hutchings
2011-11-16 5:53 ` [PATCH 3/5] staging: lirc_serial: Fix deadlock on resume failure Ben Hutchings
2011-11-16 5:53 ` [PATCH 4/5] staging: lirc_serial: Fix bogus error codes Ben Hutchings
2011-11-16 5:54 ` [PATCH 5/5] staging: lirc_serial: Do not assume error codes returned by request_irq() Ben Hutchings
2012-03-02 3:45 ` [PATCH 1/5] staging: lirc_serial: Fix init/exit order Jonathan Nieder
2012-03-02 4:35 ` Ben Hutchings
2012-03-02 5:29 ` VDR User
2012-03-02 20:39 ` [PATCH 3.0.y 0/4] Re: lirc_serial spuriously claims assigned port and irq to be in use Jonathan Nieder
2012-03-02 20:40 ` [PATCH 1/4] [media] staging: lirc_serial: Fix init/exit order Jonathan Nieder
2012-03-02 20:40 ` [PATCH 2/4] [media] staging: lirc_serial: Free resources on failure paths of lirc_serial_probe() Jonathan Nieder
2012-03-02 20:41 ` [PATCH 3/4] [media] staging: lirc_serial: Fix deadlock on resume failure Jonathan Nieder
2012-03-02 20:41 ` [PATCH 4/4] [media] staging: lirc_serial: Do not assume error codes returned by request_irq() Jonathan Nieder
2012-03-02 21:13 ` [PATCH 3.0.y 0/4] Re: lirc_serial spuriously claims assigned port and irq to be in use Greg Kroah-Hartman
2012-03-03 1:13 ` Jonathan Nieder
2012-03-07 20:04 ` Greg Kroah-Hartman
2012-03-07 20:17 ` Jonathan Nieder
2012-03-08 18:34 ` Greg Kroah-Hartman
2012-03-07 21:34 ` Ben Hutchings [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120307213441.GX12704@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jarod@redhat.com \
--cc=jrnieder@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=torsten.crass@eBiology.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox