From: David Miller <davem@davemloft.net>
To: broonie@kernel.org
Cc: jakub.kicinski@netronome.com, simon.horman@netronome.com,
oss-drivers@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH] nfp: Explicitly include linux/bug.h
Date: Sat, 14 Oct 2017 18:31:52 -0700 (PDT) [thread overview]
Message-ID: <20171014.183152.556133969386350823.davem@davemloft.net> (raw)
In-Reply-To: <20171013025035.4450-1-broonie@kernel.org>
From: Mark Brown <broonie@kernel.org>
Date: Fri, 13 Oct 2017 03:50:35 +0100
> Today's -next build encountered an error due to a missing definition of
> WARN_ON(), caused by some header reorganization removing an implicit
> inclusion of linux/bug.h. Fix this with an explicit inclusion.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Applied, thanks Mark.
prev parent reply other threads:[~2017-10-15 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 2:50 [PATCH] nfp: Explicitly include linux/bug.h Mark Brown
2017-10-13 3:16 ` Jakub Kicinski
2017-10-15 1:31 ` David Miller [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=20171014.183152.556133969386350823.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=broonie@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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;
as well as URLs for NNTP newsgroup(s).