From: Kirill Korotaev <dev@sw.ru>
To: "Fernando Luis Vбzquez Cao" <fernando@oss.ntt.co.jp>
Cc: Greg KH <gregkh@suse.de>, Greg KH <greg@kroah.com>,
"Luck, Tony" <tony.luck@intel.com>,
akpm@osdl.org, dev@openvz.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net,
stable@kernel.org, kamezawa.hiroyu@jp.fujitsu.com,
xemul@openvz.org
Subject: Re: [stable] [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3)
Date: Mon, 04 Sep 2006 14:30:57 +0400 [thread overview]
Message-ID: <44FC0061.1000007@sw.ru> (raw)
In-Reply-To: <1157364634.3162.8.camel@sebastian.intellilink.co.jp>
Fernando,
I planned to send it today. You will be on CC
Thanks,
Kirill
> On Tue, 2006-08-29 at 09:08 -0700, Greg KH wrote:
>
>>On Tue, Aug 29, 2006 at 04:24:21PM +0400, Kirill Korotaev wrote:
>>
>>>Probably it is my fault, since I thought that patches which got into -stable
>>>automatically go into Linus tree.
>>
>>No they do not. Usually it's the requirement that they be in his tree
>>first, but I didn't think it was necessary this time due to my
>>misunderstanding about the fix.
>
> 2.6.18-rc6 has just been released and neither my patch nor the original
> patch to which it is a fix seem to have been included. Does this mean
> they will not be sent to Linux before the final release of 2.6.18?
>
> Regards,
>
> Fernando
>
>
--
VGER BF report: H 0
next prev parent reply other threads:[~2006-09-04 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 22:11 [PATCH] Linux 2.6.17.11 - fix compilation error on IA64 (try #3) Luck, Tony
2006-08-29 1:31 ` [stable] " Greg KH
2006-08-29 12:24 ` Kirill Korotaev
2006-08-29 16:08 ` Greg KH
2006-09-04 10:10 ` Fernando Luis Vázquez Cao
2006-09-04 10:30 ` Kirill Korotaev [this message]
2006-08-29 12:24 ` Kirill Korotaev
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 8:13 Fernando Vazquez
2006-08-25 22:07 ` [stable] " 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=44FC0061.1000007@sw.ru \
--to=dev@sw.ru \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=fernando@oss.ntt.co.jp \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tony.luck@intel.com \
--cc=xemul@openvz.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