public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <rdunlap@infradead•org>,
	David Miller <davem@davemloft•net>,
	netdev@vger•kernel.org, Peter Foley <pefoley2@pefoley•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Willem de Bruijn <willemb@google•com>
Subject: linux-next: manual merge of the rd-docs tree with the net-next tree
Date: Mon, 8 Sep 2014 17:59:13 +1000	[thread overview]
Message-ID: <20140908175913.42603191@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Hi Randy,

Today's linux-next merge of the rd-docs tree got a conflict in
Documentation/networking/timestamping/Makefile between commit
8fe2f761cae9 ("net-timestamp: expand documentation") from the net-next
tree and commits 429cbe7863ad ("Documentation: use subdir-y to avoid
unnecessary built-in.o files") and b07a884ea14d ("Documentation: add
makefiles for more targets") from the rd-docs tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc Documentation/networking/timestamping/Makefile
index 95e239c70076,52ac67da9315..000000000000
--- a/Documentation/networking/timestamping/Makefile
+++ b/Documentation/networking/timestamping/Makefile
@@@ -1,20 -1,8 +1,14 @@@
 +# To compile, from the source root
 +#
 +#    make headers_install
 +#    make M=documentation
 +
- # kbuild trick to avoid linker error. Can be omitted if a module is built.
- obj- := dummy.o
- 
  # List of programs to build
- hostprogs-y := timestamping txtimestamp hwtstamp_config
 -hostprogs-y := hwtstamp_config timestamping
++hostprogs-y := hwtstamp_config timestamping txtimestamp
  
  # Tell kbuild to always build the programs
  always := $(hostprogs-y)
  
  HOSTCFLAGS_timestamping.o += -I$(objtree)/usr/include
 +HOSTCFLAGS_txtimestamp.o += -I$(objtree)/usr/include
  HOSTCFLAGS_hwtstamp_config.o += -I$(objtree)/usr/include
- 
- clean:
- 	rm -f timestamping txtimestamp hwtstamp_config

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2014-09-08  7:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140908175913.42603191@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pefoley2@pefoley$(echo .)com \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=willemb@google$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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