All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/2] Remove unneeded stddef.h includes
Date: Sun,  5 Feb 2017 16:07:31 +0900	[thread overview]
Message-ID: <cover.1486276931.git.shorne@gmail.com> (raw)

Hi All,

These were causing openrisc build to fail when building with allyesconfig
using a musl toolchain.  Removing them doesnt seem to cause any issues. 

The line removed was:

  #include <stddef.h>

Perhaps what was wanted was 'linux/stddef.h' but there did seem to be any
special uses so I just removed it.  Also, sending these patches should help
the kbuild robots verify that.

If I can get acks I will push it in with my openrisc branch.  But if this
should got through the net and staging paths I am happy with that.

-Stafford

Stafford Horne (2):
  libceph: Remove unneeded stddef.h include
  staging: vchip_shim: Remove unneeded stddef.h include

 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_shim.c | 2 --
 net/ceph/snapshot.c                                            | 2 --
 2 files changed, 4 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-02-05  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05  7:07 Stafford Horne [this message]
2017-02-05  7:07 ` [PATCH 1/2] libceph: Remove unneeded stddef.h include Stafford Horne
2017-02-06 10:19   ` Ilya Dryomov
2017-02-06 16:16   ` David Laight
2017-02-07  2:45     ` Stafford Horne
2017-02-05  7:07 ` [PATCH 2/2] staging: vchip_shim: " Stafford Horne
2017-02-05  7:07   ` Stafford Horne

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=cover.1486276931.git.shorne@gmail.com \
    --to=shorne@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.