public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: maximilian attems <mattems@hep.itp.tuwien.ac.at>
Cc: linux-kbuild@vger.kernel.org, Michael Prokop <mika@debian.org>,
	maximilian attems <max@stro.at>
Subject: Re: [PATCH] deb-pkg: Add all Makefiles to header package
Date: Thu, 28 Jun 2012 10:49:52 +0200	[thread overview]
Message-ID: <4FEC1AB0.9080200@suse.cz> (raw)
In-Reply-To: <1339148186-14123-1-git-send-email-mattems@hep.itp.tuwien.ac.at>

On 8.6.2012 11:36, maximilian attems wrote:
> From: maximilian attems <max@stro.at>
> 
> I discovered that make deb-pkg does not add Makefile_32.cpu from
> arch/x86 directory when doing i386 kernel build and package build.
> Fix it by greedily adding all Makefiles.
> 
> Reported-by: Witold Baryluk <baryluk@smp.if.uj.edu.pl>
> Signed-off-by: maximilian attems <max@stro.at>

Applied to kbuild.git#misc, thanks.

Michal

      reply	other threads:[~2012-06-28  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08  9:36 [PATCH] deb-pkg: Add all Makefiles to header package maximilian attems
2012-06-28  8:49 ` Michal Marek [this message]

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=4FEC1AB0.9080200@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mattems@hep.itp.tuwien.ac.at \
    --cc=max@stro.at \
    --cc=mika@debian.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