From: Jonathan Nieder <jrnieder@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
Jarod Wilson <jarod@redhat.com>,
Torsten Crass <torsten.crass@eBiology.de>
Subject: [PATCH 3.0.y 0/4] Re: lirc_serial spuriously claims assigned port and irq to be in use
Date: Fri, 2 Mar 2012 14:39:13 -0600 [thread overview]
Message-ID: <20120302203913.GA22323@burratino> (raw)
In-Reply-To: <1330662942.8460.229.camel@deadeye>
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.
Ben Hutchings (4):
[media] staging: lirc_serial: Fix init/exit order
[media] staging: lirc_serial: Free resources on failure paths of
lirc_serial_probe()
[media] staging: lirc_serial: Fix deadlock on resume failure
[media] staging: lirc_serial: Do not assume error codes returned by
request_irq()
drivers/staging/lirc/lirc_serial.c | 100 +++++++++++++++++-------------------
1 file changed, 47 insertions(+), 53 deletions(-)
next prev parent reply other threads:[~2012-03-02 20:39 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 ` Jonathan Nieder [this message]
2012-03-02 20:40 ` [PATCH 1/4] [media] " 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
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=20120302203913.GA22323@burratino \
--to=jrnieder@gmail.com \
--cc=ben@decadent.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jarod@redhat.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