LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Frank Haverkamp <haver@vnet.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, Frank Haverkamp <haver@vnet.ibm.com>
Subject: Re: [PATCH] Fix missing include of list.h in sysfs.h
Date: Thu, 18 Jan 2007 09:25:45 +0100	[thread overview]
Message-ID: <1169108745.4231.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20070117211447.GA32495@kroah.com>

Hi Greg,

On Wed, 2007-01-17 at 13:14 -0800, Greg KH wrote:

> Does this currently cause a build error on any platform for 2.6.20-rc5?

Not that I know of. I saw it because a friend of mine tried to port
some old code and played with the include ordering. Somehow he got
a compile error doing it, and we found that it is strange that sysfs.h
is using structs from list.h but is not including it. As result I sent
the patch to propose that it gets included to avoid any possible
trouble.

Frank


      reply	other threads:[~2007-01-18  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 16:51 Frank Haverkamp
2007-01-17 21:14 ` Greg KH
2007-01-18  8:25   ` Frank Haverkamp [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=1169108745.4231.6.camel@localhost.localdomain \
    --to=haver@vnet.ibm.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] Fix missing include of list.h in sysfs.h' \
    /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).