ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Should we force include <linux/err.h> when compiling all .c files?
Date: Tue, 29 Jul 2014 12:06:01 -0700	[thread overview]
Message-ID: <CANsGZ6beZ4D6eVT0M4EqoA1xboeTTOUuoEk5SfpCyGX+LUFY8Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1407290938040.4599@eggly.anvils>

On Tue, Jul 29, 2014 at 9:50 AM, Hugh Dickins <hughd@google.com> wrote:
> And our response to that is to get the kbuild system to include
> automatically any header files frequently forgotten?

Sorry, that was an initial suggestion which the discussion quickly
moved away from.  But I still don't understand why the inclusion of
linux/err.h is a matter of such interest.  How  best to make sweeping
changes, sure; but why to bother to do so for linux/err.h remains a
mystery to me.

Hugh

  reply	other threads:[~2014-07-29 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 12:39 David Howells
2014-07-25 23:24 ` Josh Triplett
2014-07-28 18:52   ` H. Peter Anvin
2014-07-28 20:16     ` Julia Lawall
2014-07-28 22:53       ` H. Peter Anvin
2014-07-29 14:35         ` Josh Triplett
2014-07-29 15:17           ` Luck, Tony
2014-07-29 16:50             ` Hugh Dickins
2014-07-29 19:06               ` Hugh Dickins [this message]
2014-07-29 14:24     ` Josh Triplett
2014-07-30 14:30       ` H. Peter Anvin

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=CANsGZ6beZ4D6eVT0M4EqoA1xboeTTOUuoEk5SfpCyGX+LUFY8Q@mail.gmail.com \
    --to=hughd@google.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=tony.luck@intel.com \
    /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