From: Adrian Bunk <bunk@stusta.de>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
stable@kernel.org
Subject: Re: Linux 2.6.12.3
Date: Sat, 16 Jul 2005 19:02:02 +0200 [thread overview]
Message-ID: <20050716170202.GA3613@stusta.de> (raw)
In-Reply-To: <20050716044815.GA10063@kroah.com>
On Fri, Jul 15, 2005 at 09:48:16PM -0700, Greg KH wrote:
>...
> Summary of changes from v2.6.12.2 to v2.6.12.3
> ==============================================
>...
> Ralf Baechle:
> SMP fix for 6pack driver
>...
Will this patch [1] also be forward-ported to Linus' tree, or will
2.6.12.3 stay the _only_ 2.6 kernel that ever offered this driver for
SMP configs?
cu
Adrian
[1] "fix" is a wrong patch description since all it does is to remove
the BROKEN_ON_SMP dependency
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2005-07-16 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 4:48 Linux 2.6.12.3 Greg KH
2005-07-16 4:49 ` Greg KH
2005-07-16 17:02 ` Adrian Bunk [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=20050716170202.GA3613@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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