From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: netdev <netdev@vger.kernel.org>,
davem@davemloft.net, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Linux 2.6.26.4
Date: Mon, 8 Sep 2008 08:21:14 -0700 [thread overview]
Message-ID: <20080908152114.GA8941@suse.de> (raw)
In-Reply-To: <20080908081253.d3100d88.randy.dunlap@oracle.com>
On Mon, Sep 08, 2008 at 08:12:53AM -0700, Randy Dunlap wrote:
> On Mon, 8 Sep 2008 07:36:25 -0700 Greg KH wrote:
>
> > We (the -stable team) are announcing the release of the 2.6.26.4
> > kernel.
> >
> > It contains lots of bugfixes, all over the map. Any users of the 2.6.26
> > kernel series should upgrade to this version. For details on the fixes,
> > see the changelog entries and the diffstat below.
> >
> > I'll also be replying to this message with a copy of the patch between
> > 2.6.26.3 and 2.6.26.4
> >
> > The updated 2.6.26.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.26.y.git
> > and can be browsed at the normal kernel.org git web browser:
> > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.26.y.git;a=summary
>
> > include/linux/pim.h | 45 -----------------
>
> That file is still used by ./net/ipv6/ip6mr.c:#include <linux/pim.h>
> so there are build errors...
Crap, I messed up, David sent me the fixed patch and I forgot it.
I'll go do a new release in a few hours...
thanks,
greg k-h
next prev parent reply other threads:[~2008-09-08 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 14:36 Linux 2.6.26.4 Greg KH
2008-09-08 14:36 ` Greg KH
2008-09-08 15:12 ` Randy Dunlap
2008-09-08 15:21 ` Greg KH [this message]
2008-09-08 16:38 ` Greg KH
2008-09-08 16:56 ` Randy Dunlap
2008-09-08 19:33 ` David Miller
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=20080908152114.GA8941@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).