From: Greg KH <greg@kroah.com>
To: "Oliver Pinter (Pint?r Oliv?r)" <oliver.pntr@gmail.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: Fri, 1 Feb 2008 16:00:39 -0800 [thread overview]
Message-ID: <20080202000039.GA25722@kroah.com> (raw)
In-Reply-To: <6101e8c40801281513p24352c4ex6c44e79aefe77696@mail.gmail.com>
On Tue, Jan 29, 2008 at 12:13:13AM +0100, Oliver Pinter (Pint?r Oliv?r) wrote:
> do_anonymous_page-race
> invalid-semicolon
> pci-fix-unterminated-pci_device_id-lists
> cciss-panic-in-blk_rq_map_sg
> cciss-fix_memory_leak
> handle-bogus-%cs-selector-in-single-step-instruction-decoding
> i386-fixup-TRACE_IRQ-breakage
> intel-agp-965gme-fix
> sony-laptop-call-sonypi_compat_init-earlier
> via-velocity-dont-oops-on-mtu-change-1
> via-velocity-dont-oops-on-mtu-change-2
> nfsacl-retval.diff
> nfs-fix-nfs-reval-fsid
> nfs-name-len-limit
> nfs-unmount-leak.patch
> nfsv4-MAXNAME-fix.diff
> nopage-range-fix.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
next prev parent reply other threads:[~2008-02-02 0:10 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 [this message]
2008-02-02 0:54 ` Oliver Pinter (Pintér Olivér)
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=20080202000039.GA25722@kroah.com \
--to=greg@kroah.com \
--cc=bunk@kernel.org \
--cc=chrisw@sous-sol.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--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®