From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: =?ISO-8859-1?Q? Ilpo_J=E4rvinen ?= <ilpo.jarvinen@helsinki.fi>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] smb.h: uses struct timespec but didn't include linux/time.h
Date: Tue, 15 Apr 2008 14:25:00 +0300 [thread overview]
Message-ID: <20080415112500.GB2454@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080415021057.9bdff72f.akpm@linux-foundation.org>
On Tue, Apr 15, 2008 at 02:10:57AM -0700, Andrew Morton wrote:
> On Tue, 15 Apr 2008 12:04:04 +0300 (EEST) "Ilpo J__rvinen" <ilpo.jarvinen@helsinki.fi> wrote:
>
> >
> > Signed-off-by: Ilpo J__rvinen <ilpo.jarvinen@helsinki.fi>
> > ---
> > include/linux/smb.h | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/smb.h b/include/linux/smb.h
> > index f098dff..caa43b2 100644
> > --- a/include/linux/smb.h
> > +++ b/include/linux/smb.h
> > @@ -11,6 +11,7 @@
> >
> > #include <linux/types.h>
> > #include <linux/magic.h>
> > +#include <linux/time.h>
> >
> > enum smb_protocol {
> > SMB_PROTOCOL_NONE,
>
> Did this actually cause a compilation error?
Even if it doesn't at the moment it should be fixed - these kind
of issues are why often adding or removing an #include in a header
suddenly breaks some configuration on some other architecture.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-15 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 9:04 Ilpo Järvinen
2008-04-15 9:10 ` Andrew Morton
2008-04-15 9:20 ` Ilpo Järvinen
2008-04-15 11:25 ` Adrian Bunk [this message]
2008-04-15 11:37 ` Ilpo Järvinen
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=20080415112500.GB2454@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ilpo.jarvinen@helsinki.fi \
--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
all inboxes | Powered by JetHome®