From: Greg KH <greg@kroah.com>
To: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] 2/10 2.4.22-rc2 fix __FUNCTION__ warnings drivers/hotplug
Date: Thu, 21 Aug 2003 22:20:00 -0700 [thread overview]
Message-ID: <20030822052000.GA7589@kroah.com> (raw)
In-Reply-To: <20030821012932.7179f30c.vmlinuz386@yahoo.com.ar>
On Thu, Aug 21, 2003 at 01:29:32AM -0300, Gerardo Exequiel Pozzi wrote:
> cpqphp.h | 6 ++--
> cpqphp_core.c | 30 +++++++++++------------
> cpqphp_ctrl.c | 68 ++++++++++++++++++++++++++---------------------------
> cpqphp_nvram.c | 2 -
> cpqphp_pci.c | 12 ++++-----
> pci_hotplug_core.c | 2 -
> pci_hotplug_util.c | 2 -
> 7 files changed, 61 insertions(+), 61 deletions(-)
>
> http://www.vmlinuz.com.ar/slackware/patch/kernel/drivers.hotplug.patch
> http://www.vmlinuz.com.ar/slackware/patch/kernel/drivers.hotplug.patch.asc
$ wget http://www.vmlinuz.com.ar/slackware/patch/kernel/drivers.hotplug.patch
--22:18:07-- http://www.vmlinuz.com.ar/slackware/patch/kernel/drivers.hotplug.patch
=> `drivers.hotplug.patch'
Resolving www.vmlinuz.com.ar... done.
Connecting to www.vmlinuz.com.ar[65.200.24.183]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
22:18:36 ERROR 404: Not Found.
Please send send patches inline in email messages to the maintainers of
the code that you are modifying, like Documentation/SubmittingPatches
says to.
thanks,
greg k-h
next prev parent reply other threads:[~2003-08-22 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 4:29 [PATCH] 2/10 2.4.22-rc2 fix __FUNCTION__ warnings drivers/hotplug Gerardo Exequiel Pozzi
2003-08-22 5:20 ` Greg KH [this message]
2003-08-22 6:10 ` Gerardo Exequiel Pozzi
2003-08-22 6:34 ` Willy Tarreau
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=20030822052000.GA7589@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=vmlinuz386@yahoo.com.ar \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.