From: Timur Tabi <timur@freescale.com>
To: Greg Kroah-Hartman <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Patch for 2.6.37.1
Date: Thu, 6 Jan 2011 14:03:22 -0600 [thread overview]
Message-ID: <4D26200A.6040208@freescale.com> (raw)
Greg,
What is the process for getting a patch into 2.6.37.1? I posted this patch last
month, hoping it would get into 2.6.37, but I was too late:
http://patchwork.ozlabs.org/patch/74171/
This patch will make it into 2.6.38. I am hoping it will also go into 2.6.37.1,
but I've never submitted a patch for a maintenance release of the kernel.
Without this patch, audio is completely non-functional on the Freescale P1022DS
reference board. I have no explanation why I didn't notice earlier that the
device tree for the board was wrong.
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2011-01-06 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 20:03 Timur Tabi [this message]
2011-01-06 20:10 ` Patch for 2.6.37.1 Greg KH
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=4D26200A.6040208@freescale.com \
--to=timur@freescale.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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