mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fathi.boudra@linaro.org, mmarek@suse.cz,
	yamada.m@jp.panasonic.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] kbuild fixes for v3.16-rc2
Date: Wed, 18 Jun 2014 23:36:22 +0200	[thread overview]
Message-ID: <20140618213622.GA21153@pobox.suse.cz> (raw)

Hi Linus,

There are three fixes for regressions caused by the relative paths
series: deb-pkg, tar-pkg and *docs did not work with O=. Plus, there is
a fix for the linux-headers deb package and a fixed typo. These are not
regression fixes but are safe enough.

Thanks,
Michal

The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:

  Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git rc-fixes

for you to fetch changes up to c14105628b2e2eee04b2d6950e068eeddf49f2f1:

  kbuild: fix a typo in a kbuild document (2014-06-18 21:38:18 +0200)

----------------------------------------------------------------
Fathi Boudra (1):
      builddeb: fix missing headers in linux-headers package

Masahiro Yamada (1):
      kbuild: fix a typo in a kbuild document

Michal Marek (3):
      deb-pkg: Fix for relative paths
      kbuild: Fix tar-pkg with relative $(objtree)
      Documentation: Fix DocBook build with relative $(srctree)

 Documentation/DocBook/media/Makefile |  4 ++--
 Documentation/kbuild/makefiles.txt   |  2 +-
 scripts/package/builddeb             | 14 ++++++++------
 scripts/package/buildtar             |  3 +--
 4 files changed, 12 insertions(+), 11 deletions(-)

                 reply	other threads:[~2014-06-18 21:36 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=20140618213622.GA21153@pobox.suse.cz \
    --to=mmarek@suse.cz \
    --cc=fathi.boudra@linaro.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yamada.m@jp.panasonic.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

all inboxes | Powered by JetHome®