From: maximilian attems <maks@stro.at>
To: Michal Marek <mmarek@suse.cz>
Cc: riku.voipio@linaro.org, linux-kbuild@vger.kernel.org,
debian-kernel@lists.debian.org
Subject: Re: [PATCH] deb-pkg: v2: move setting debarch for a separate function
Date: Wed, 22 Apr 2015 17:52:01 +0200 [thread overview]
Message-ID: <20150422155201.GB32026@gluino> (raw)
In-Reply-To: <5537B412.1000109@suse.cz>
On Wed, Apr 22, 2015 at 04:45:38PM +0200, Michal Marek wrote:
> On 2015-04-16 15:42, riku.voipio@linaro.org wrote:
> > From: Riku Voipio <riku.voipio@linaro.org>
> >
> > create_package() function tries to resolve used architecture
> > for everry package. Split the setting the architecture to a
> > new function, set_debarch(), called once on startup.
> >
> > This allows using debarch from other parts of script as
> > needed.
> >
> > v2: Follow Michals suggestion on setting variables at
> > top scope and also setting the fallback $debarch in the
> > new function
> >
> > Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
>
> Thanks, applied to kbuild.git#misc. But please base your patches on
> Linus's or the maintainer's tree next time. Your patch had some
> conflicts, because it was based on some non-upstream patches.
thanks, acked.
prev parent reply other threads:[~2015-04-22 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 13:15 [PATCH 1/2] deb-pkg: move setting debarch for a separate function riku.voipio
2015-04-10 13:15 ` [PATCH 2/2] deb-pkg: add source package riku.voipio
2015-04-22 15:50 ` maximilian attems
2015-04-23 9:01 ` Riku Voipio
2015-04-23 10:43 ` maximilian attems
2015-04-15 12:30 ` [PATCH 1/2] deb-pkg: move setting debarch for a separate function Michal Marek
2015-04-16 13:42 ` [PATCH] deb-pkg: v2: " riku.voipio
2015-04-22 14:45 ` Michal Marek
2015-04-22 15:52 ` maximilian attems [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=20150422155201.GB32026@gluino \
--to=maks@stro.at \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=riku.voipio@linaro.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;
as well as URLs for NNTP newsgroup(s).