From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [OP] linux v2.6.22.21-op1
Date: Sat, 5 Apr 2008 15:24:13 +0200 [thread overview]
Message-ID: <6101e8c40804050624u4b902096q867f231f8aa13d1c@mail.gmail.com> (raw)
In-Reply-To: <6101e8c40804050622k18fde2f5p73c42d27a3189fe3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3133 bytes --]
and the patch
On 4/5/08, Oliver Pinter <oliver.pntr@gmail.com> wrote:
> I announced the v2.6.22.21-op1 "stable" kernel.
>
> gitweb: http://repo.or.cz/w/linux-2.6.22.y-op.git
> git-tree: git://repo.or.cz/linux-2.6.22.y-op.git
> patches-gitweb : http://repo.or.cz/w/linux-2.6.22.y-op-patches.git
> tar-bz2:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/v2.6.22.21-op1.tar.bz2
> patch:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/patch-v2.6.22.20-op1-v2.6.22.21-op1.bz2
> chlog:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/chlog-v2.6.22.21-op1
> ======================================
>
> Makefile | 2 +-
> drivers/md/raid5.c | 14 ++---
> drivers/net/tulip/tulip_core.c | 4 +
> fs/cifs/cifs_debug.c | 92 +++--------------------------
> fs/cifs/cifsglob.h | 11 ++++
> fs/cifs/cifsproto.h | 4 +-
> fs/cifs/cifssmb.c | 130
> ++++++++++++++++++----------------------
> fs/cifs/connect.c | 9 ++-
> fs/cifs/file.c | 14 ++--
> fs/cifs/sess.c | 3 +-
> fs/cifs/transport.c | 88 +++++++++++++++++++++------
> mm/slab.c | 5 +-
> 12 files changed, 174 insertions(+), 202 deletions(-)
>
> ======================================
> gitweb: http://repo.or.cz/w/linux-2.6.22.y-op.git
> git-tree: git://repo.or.cz/linux-2.6.22.y-op.git
> patches-gitweb : http://repo.or.cz/w/linux-2.6.22.y-op-patches.git
> tar-bz2:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/v2.6.22.21-op1.tar.bz2
> patch:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/patch-v2.6.22.20-op1-v2.6.22.21-op1.bz2
> chlog:
> http://students.zipernowsky.hu/~oliverp/kernel-stable/chlog-v2.6.22.21-op1
> ======================================
>
> Makefile | 2 +-
> drivers/md/raid5.c | 14 ++---
> drivers/net/tulip/tulip_core.c | 4 +
> fs/cifs/cifs_debug.c | 92 +++--------------------------
> fs/cifs/cifsglob.h | 11 ++++
> fs/cifs/cifsproto.h | 4 +-
> fs/cifs/cifssmb.c | 130
> ++++++++++++++++++----------------------
> fs/cifs/connect.c | 9 ++-
> fs/cifs/file.c | 14 ++--
> fs/cifs/sess.c | 3 +-
> fs/cifs/transport.c | 88 +++++++++++++++++++++------
> mm/slab.c | 5 +-
> 12 files changed, 174 insertions(+), 202 deletions(-)
>
> ======================================
>
> Joe Korty (1):
> slab: NUMA slab allocator migration bugfix
>
> NeilBrown (1):
> md: fix an occasional deadlock in raid5
>
> Oliver Pinter (1):
> v2.6.22.21-op1
>
> Steve French (2):
> Fix buffer overflow if server sends corrupt response to small
> Fix sign mount option and sign proc config setting
>
> andrew.patterson@hp.com (1):
> MCA when shutting down tulip quad-NIC
>
> ======================================
> Thanks,
> Oliver
> /* http://students.zipernowsky.hu/~oliverp/ */
>
--
Thanks,
Oliver
[-- Attachment #2: patch-v2.6.22.20-op1-v2.6.22.21-op1.bz2 --]
[-- Type: application/x-bzip2, Size: 7968 bytes --]
prev parent reply other threads:[~2008-04-05 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 13:22 Oliver Pinter
2008-04-05 13:24 ` Oliver Pinter [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=6101e8c40804050624u4b902096q867f231f8aa13d1c@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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®