mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Osmialowski <p.osmialowsk@samsung.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Daniel Mack <daniel@zonque.org>,
	David Herrmann <dh.herrmann@googlemail.com>,
	Djalal Harouni <tixxdz@opendz.org>,
	Paul Moore <pmoore@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: Paul Osmialowski <p.osmialowsk@samsung.com>,
	Lukasz Pawelczyk <l.pawelczyk@samsung.com>
Subject: [PATCH 01/01] kdbus: Eliminate warning caused by lack of uapi/linux/kdbus.h inclusion
Date: Tue, 08 Sep 2015 14:48:34 +0200	[thread overview]
Message-ID: <1441716514-3572-2-git-send-email-p.osmialowsk@samsung.com> (raw)
In-Reply-To: <1441716514-3572-1-git-send-email-p.osmialowsk@samsung.com>

metadata.h references struct kdbus_pids which is defined in
uapi/linux/kdbus.h

Normally, kdbus/metadata.h is included after many other headers
that eventually include uapi/linux/kdbus.h at some point (e.g. kdbus/bus.h
includes uapi/linux/kdbus.h), this prevents the warning.

When included alone, it causes warning. Also when kdbus/connection.h
is included alone, the same warning is shown since kdbus/connection.h
includes kdbus/metadata.h.

This patch adds missing inclusion.

Signed-off-by: Paul Osmialowski <p.osmialowsk@samsung.com>
---
 ipc/kdbus/metadata.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/ipc/kdbus/metadata.h b/ipc/kdbus/metadata.h
index dba7cc7..3f9ba38 100644
--- a/ipc/kdbus/metadata.h
+++ b/ipc/kdbus/metadata.h
@@ -16,6 +16,7 @@
 #define __KDBUS_METADATA_H
 
 #include <linux/kernel.h>
+#include <uapi/linux/kdbus.h>
 
 struct kdbus_conn;
 struct kdbus_pool_slice;
-- 
1.9.1


  reply	other threads:[~2015-09-08 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 12:48 [PATCH 00/01] " Paul Osmialowski
2015-09-08 12:48 ` Paul Osmialowski [this message]
2015-09-08 12:54   ` [PATCH 01/01] " David Herrmann

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=1441716514-3572-2-git-send-email-p.osmialowsk@samsung.com \
    --to=p.osmialowsk@samsung.com \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=l.pawelczyk@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmoore@redhat.com \
    --cc=tixxdz@opendz.org \
    /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®