From: Randy Dunlap <randy.dunlap@oracle.com>
To: Willy Tarreau <wtarreau@hera.kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.20.17
Date: Sat, 25 Aug 2007 11:01:48 -0700 [thread overview]
Message-ID: <20070825110148.5fd59272.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070825153810.GA32619@hera.kernel.org>
On Sat, 25 Aug 2007 15:38:10 +0000 Willy Tarreau wrote:
>
> I've just released Linux 2.6.20.17.
>
> As a reminder, it fixes these 3 security issues :
> CVE-2007-3105
> CVE-2007-3848
> CVE-2007-3851
>
> I'll also be replying to this message with a copy of the patch between
> 2.6.20.16 and 2.6.20.17.
>
> The patch and changelog will appear soon at the following locations:
> ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/
> ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.17.bz2
> ftp://ftp.all.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.20.17
>
> Git repository:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.git
> http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.20.y.git
>
> Git repository through the gitweb interface:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git
I'm getting build errors:
x86_64 allyesconfig, allmodconfig:
drivers/ata/pata_atiixp.c:286: error: 'PCI_DEVICE_ID_ATI_IXP700_IDE' undeclared here (not in a function)
net/bluetooth/rfcomm/tty.c:275: error: 'struct rfcomm_dev' has no member named 'tty_dev'
net/bluetooth/rfcomm/tty.c:278: error: 'struct rfcomm_dev' has no member named 'tty_dev'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-08-25 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 15:38 Willy Tarreau
2007-08-25 15:41 ` Willy Tarreau
2007-08-25 18:01 ` Randy Dunlap [this message]
2007-08-26 15:15 ` Boris B. Zhmurov
2007-08-26 15:48 ` Marcel Holtmann
2007-08-27 1:12 ` Willy Tarreau
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=20070825110148.5fd59272.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wtarreau@hera.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
all inboxes | Powered by JetHome®