public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-kernel@vger.kernel.org
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH] extable.h: add stddef.h so "NULL" definition is not implicit
Date: Thu, 28 Jul 2016 15:24:39 +0930	[thread overview]
Message-ID: <878twmz4rk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20160728031147.26362-1-paul.gortmaker@windriver.com>

Paul Gortmaker <paul.gortmaker@windriver.com> writes:
> While not an issue now, eventually we will have independent users of
> the extable.h file and we will stop sourcing it via module.h header.
>
> In testing that pending work, with very sparse builds, characteristic
> of an "allnoconfig" on various architectures, we can sometimes hit an
> instance where the very basic standard definitions aren't present,
> resulting in:
>
>  include/linux/extable.h:26:9: error: 'NULL' undeclared (first use in this function)
>
> To be clear, this isn't a regression, since currently extable.h is
> only used by module.h -- however, we will need this addition present
> before we start migrating exception table users off module.h and onto
> extable.h during the next release cycle.
>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
>
> [Was not expecting extable.h to be in 4.8 content, but since it is, it
>  might as well have this one line fixup to make it ready for 4.9 ; feel
>  free to squash this into the original extable.h creation if rebasing.]

Applied.  I prefer not to rebase published trees, and it's not like it's
going to break anyone's bisect.

Thanks,
Rusty.

      reply	other threads:[~2016-07-28  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28  3:11 [PATCH] extable.h: add stddef.h so "NULL" definition is not implicit Paul Gortmaker
2016-07-28  5:54 ` Rusty Russell [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=878twmz4rk.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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