public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Greg KH <greg@kroah.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org
Subject: Re: Still get build warnings - gcc-3.4.6 - 2.6.17.8
Date: Wed, 9 Aug 2006 18:38:44 +0100	[thread overview]
Message-ID: <200608091838.44989.nick@linicks.net> (raw)
In-Reply-To: <20060808231915.GA23161@kroah.com>

On Wednesday 09 August 2006 00:19, Greg KH wrote:

> > fwiw, I don't seem to have any patches to fix/remove them.
>
> pm_unregister_all is removed in the -mm tree, from a patch in my tree.
>

OK, thanks all.  For love nor money could I find the mail/patch somebody sent 
me ages ago for this... but anyway, it's been sorted now.

Nick
-- 
Every program has two purposes:
one for which it was written and another for which it wasn't.

      reply	other threads:[~2006-08-09 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 20:48 Still get build warnings - gcc-3.4.6 - 2.6.17.8 Nick Warne
2006-08-08 21:12 ` Randy.Dunlap
2006-08-08 22:15   ` Sam Ravnborg
2006-08-08 23:19   ` Greg KH
2006-08-09 17:38     ` Nick Warne [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=200608091838.44989.nick@linicks.net \
    --to=nick@linicks.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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