public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] include stddef.h in include/linux/list.h
Date: Sun, 16 Mar 2003 01:24:04 +1000	[thread overview]
Message-ID: <3E734594.3080508@snapgear.com> (raw)
In-Reply-To: <20030311153859.A17036@redhat.com>

Hi Benjamin,

Benjamin LaHaise wrote:
> On Tue, Mar 11, 2003 at 05:47:54PM +0000, Linux Kernel Mailing List wrote:
> 
>>diff -Nru a/include/linux/list.h b/include/linux/list.h
>>--- a/include/linux/list.h	Tue Mar 11 11:07:05 2003
>>+++ b/include/linux/list.h	Tue Mar 11 11:07:05 2003
>>@@ -3,6 +3,7 @@
>> 
>> #ifdef __KERNEL__
>> 
>>+#include <linux/stddef.h>
>> #include <linux/prefetch.h>
>> #include <linux/stddef.h>
>> #include <asm/system.h>
> 
> 
> Huh?  Surely you meant to delete the extra stddef.h include...

No the original patch included stddef.h, when none was included.
Obviously 2 patch sets have been applied post 2.5.64 that are
trying to do the same thing.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Wizard        EMAIL:  gerg@snapgear.com
SnapGear Pty Ltd                               PHONE:    +61 7 3435 2888
825 Stanley St,                                  FAX:    +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia              WEB:   www.SnapGear.com


      reply	other threads:[~2003-03-15 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200303111907.h2BJ72502778@hera.kernel.org>
2003-03-11 20:38 ` [PATCH] include stddef.h in include/linux/list.h Benjamin LaHaise
2003-03-15 15:24   ` Greg Ungerer [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=3E734594.3080508@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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