All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Mark Brown <broonie@kernel.org>
Cc: davem@davemloft.net, Simon Horman <simon.horman@netronome.com>,
	oss-drivers@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH] nfp: Explicitly include linux/bug.h
Date: Thu, 12 Oct 2017 20:16:43 -0700	[thread overview]
Message-ID: <20171012201643.08ff9f4f@cakuba.netronome.com> (raw)
In-Reply-To: <20171013025035.4450-1-broonie@kernel.org>

On Fri, 13 Oct 2017 03:50:35 +0100, Mark Brown wrote:
> 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>

Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>

Thank you!

  reply	other threads:[~2017-10-13  3:16 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 [this message]
2017-10-15  1:31 ` David Miller

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=20171012201643.08ff9f4f@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=broonie@kernel.org \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.