mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	stable@kernel.org, stable-commits@vger.kernel.org,
	"chrisw@sous-sol.org" <chrisw@sous-sol.org>,
	"Greg KH" <gregkh@suse.de>, "Willy Tarreau" <w@1wt.eu>,
	"Adrian Bunk" <bunk@kernel.org>
Subject: Re: [2.6.22.y] {00/17} series for stable kernel
Date: Sat, 2 Feb 2008 01:54:44 +0100	[thread overview]
Message-ID: <6101e8c40802011654l2630ef1ewe45c0a341f2ab2af@mail.gmail.com> (raw)
In-Reply-To: <20080202000039.GA25722@kroah.com>

hi!

then i searched the git id's and resnd the patches



On 2/2/08, Greg KH <greg@kroah.com> wrote:
> On Tue, Jan 29, 2008 at 12:13:13AM +0100, Oliver Pinter (Pint?r Oliv?r)
> wrote:
> > do_anonymous_page-race
NOT PART OF mainline - or I not find  - openSUSE patch

> > invalid-semicolon
2b02d13996fe28478e45605de9bd8bdca25718de

> > pci-fix-unterminated-pci_device_id-lists
248bdd5efca5a113cbf443a993c69e53d370236b

> > cciss-panic-in-blk_rq_map_sg
a683d652d334a546be9175b894f42dbd8e399536

> > cciss-fix_memory_leak
f2912a1223c0917a7b4e054f18086209137891ea

> > handle-bogus-%cs-selector-in-single-step-instruction-decoding 29eb51101c02df517ca64ec472d7501127ad1da8

> > i386-fixup-TRACE_IRQ-breakage
a10d9a71bafd3a283da240d2868e71346d2aef6f

> > intel-agp-965gme-fix
dde4787642ee3cb85aef80bdade04b6f8ddc3df8

> > sony-laptop-call-sonypi_compat_init-earlier
015a916fbbf105bb15f4bbfd80c3b9b2f2e0d7db

> > via-velocity-dont-oops-on-mtu-change-1
bd7b3f34198071d8bec05180530c362f1800ba46

> > via-velocity-dont-oops-on-mtu-change-2
48f6b053613b62fed7a2fe3255e5568260a8d615

> > nfsacl-retval.diff
ac8587dcb58e40dd336d99d60f852041e06cc3dd

> > nfs-fix-nfs-reval-fsid
a0356862bcbeb20acf64bc1a82d28a4c5bb957a7

> > nfs-name-len-limit
54af3bb543c071769141387a42deaaab5074da55

> > nfs-unmount-leak.patch
13ef7b69b54aa8ae4ed264d0bf41339737f8543a - in mainline from comment:
...skipping... ?!

> > nfsv4-MAXNAME-fix.diff
a16e92edcd0a2846455a30823e1bac964e743baa

> > nopage-range-fix.patch
NOT PART  OF the mainline - or I not find - original openSUSE patch

> >
> > this patches is from suse 10.3 kernel, the most is applyied in
> > mainline, but 2 not.
>
> But which 2 are not?  We can't add them to the -stable tree unless they
> are.
>
> Can you resend the ones that are already upstream, with the git commit
> ids?  You did that with some, but not all, and more than 2, so I really
> have no idea what to apply here.
>
> So I guess I'll drop all of these, as I really don't want to go digging
> to figure it out :(
>
> thanks,
>
> greg k-h
>


-- 
Thanks,
Oliver

      reply	other threads:[~2008-02-02  0:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 23:13 Oliver Pinter (Pintér Olivér)
2008-02-02  0:00 ` Greg KH
2008-02-02  0:54   ` Oliver Pinter (Pintér Olivér) [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=6101e8c40802011654l2630ef1ewe45c0a341f2ab2af@mail.gmail.com \
    --to=oliver.pntr@gmail.com \
    --cc=bunk@kernel.org \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=w@1wt.eu \
    /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®