mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Brownell <david-b@pacbell.net>
Cc: viro@ftp.linux.org.uk, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] missing include in mmc
Date: Wed, 17 Oct 2007 09:40:52 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710170937290.29643@anakin> (raw)
In-Reply-To: <20071017032139.17D6323A687@adsl-69-226-248-13.dsl.pltn13.pacbell.net>

On Tue, 16 Oct 2007, David Brownell wrote:
> > > > AFAICS, fallout from repacing include of blkdev.h with include of bio.h.
> > > 
> > > Out of curiousity, which architecture(s) need this?
> >
> > Umm...   IIRC, m32r had been the first build to step into that, at which point
> > the missing include had been added; the rest had reached that point later, so
> > I'm not sure which ones would trigger the same crap.  Not hard to test,
> > though...
> >
> > Aha.  m68k as well.

Yesterday I saw a similar issue with drivers/md/dm-mpath-rdac.c, but it
disappeared during the night, and I didn't see an obvious change that
fixed it...

> Every time I seee a case where architectures don't act the same
> with respect to #includes, I count it as an unpleasant surprise.
> Not one that's very easy to avoid, unfortunately, but I think it's
> been happening less often lately.

Simple rule of thumb: he who uses fields of struct xxx should include
the header file that defines struct xxx...

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

      reply	other threads:[~2007-10-17  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  0:09 Al Viro
2007-10-17  0:25 ` David Brownell
2007-10-17  2:04   ` Al Viro
2007-10-17  3:21     ` David Brownell
2007-10-17  7:40       ` Geert Uytterhoeven [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=Pine.LNX.4.64.0710170937290.29643@anakin \
    --to=geert@linux-m68k.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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®