LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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>,
	Adrian Bunk <bunk@kernel.org>, Greg KH <gregkh@suse.de>,
	Willy Tarreau <w@1wt.eu>
Subject: Re: [stable] [2.6.22.y] {00/17} series for stable kernel #2
Date: Wed, 6 Feb 2008 14:48:41 -0800	[thread overview]
Message-ID: <20080206224841.GB11045@kroah.com> (raw)
In-Reply-To: <6101e8c40802011733h3e5a4c8bgb6c1d1feb2205043@mail.gmail.com>

On Sat, Feb 02, 2008 at 02:33:10AM +0100, Oliver Pinter (Pint?r Oliv?r) wrote:
> 01/17** do_anonymous_page-race
> 02/17 invalid-semicolon
> 03/17 pci-fix-unterminated-pci_device_id-lists
> 04/17 cciss-panic-in-blk_rq_map_sg
> 05/17 cciss-fix_memory_leak
> 06/17 handle-bogus-%cs-selector-in-single-step-instruction-decoding
> 07/17 i386-fixup-TRACE_IRQ-breakage
> 08/17 intel-agp-965gme-fix
> 09/17 sony-laptop-call-sonypi_compat_init-earlier
> 10/17 via-velocity-dont-oops-on-mtu-change-1
> 11/17 via-velocity-dont-oops-on-mtu-change-2
> 12/17 nfsacl-retval.diff
> 13/17 nfs-fix-nfs-reval-fsid
> 14/17 nfs-name-len-limit
> 15/17 nfs-unmount-leak.patch
> 16/17 nfsv4-MAXNAME-fix.diff
> 17/17** nopage-range-fix.patch
> 
> 
> Patch 1 and 17 not included is mainline

All of these were in base64 format and I can't apply any of them :(

Can you please resend them with a sane email client, and take out the
ones that are not upstream yet, and remove the ones that are already in
the 2.6.24.17 release?

thanks,

greg k-h

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02  1:33 Oliver Pinter (Pintér Olivér)
2008-02-06 22:48 ` Greg KH [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=20080206224841.GB11045@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 \
    --subject='Re: [stable] [2.6.22.y] {00/17} series for stable kernel #2' \
    /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

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).