All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH 00/12] Update architecture detection
Date: Thu, 2 Aug 2018 08:10:20 +0900	[thread overview]
Message-ID: <CAK7LNAS0hZDKQmP0aLCM9j-SiWgrmGW=jP4g_x+TqGBOmnPU1w@mail.gmail.com> (raw)
In-Reply-To: <20180726101934.GT14131@decadent.org.uk>

2018-07-26 19:19 GMT+09:00 Ben Hutchings <ben@decadent.org.uk>:
> This series cleans up the set_debarch function in
> scripts/package/mkdebian and adds support for several additional
> Debian architectures.
>
> Ben.
>
> Ben Hutchings (12):
>   builddeb: Skip architecture detection when KBUILD_DEBARCH is set
>   builddeb: Change architecture detection fallback to use
>     dpkg-architecture
>   builddeb: Drop check for 32-bit s390
>   builddeb: Introduce functions to simplify kconfig tests in set_debarch
>   builddeb: Add automatic support for ppc64 and powerpcspe architectures
>   builddeb: Add automatic support for mips64el architecture
>   builddeb: Add automatic support for mips46{,64}{,el} architectures
>   builddeb: Add automatic support for sparc64 architecture
>   builddeb: Add automatic support for or1k architecture
>   builddeb: Add automatic support for m68k architecture
>   builddeb: Add automatic support for riscv* architectures
>   builddeb: Add automatic support for sh{3,4}{,eb} architectures
>
>  scripts/package/mkdebian | 68 +++++++++++++++++++++++++++++-----------
>  1 file changed, 50 insertions(+), 18 deletions(-)
>

Applied.  Thanks!


-- 
Best Regards
Masahiro Yamada

      parent reply	other threads:[~2018-08-02  0:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 10:19 [PATCH 00/12] Update architecture detection Ben Hutchings
2018-07-26 10:20 ` [PATCH 01/12] builddeb: Skip architecture detection when KBUILD_DEBARCH is set Ben Hutchings
2018-07-26 10:20 ` [PATCH 02/12] builddeb: Change architecture detection fallback to use dpkg-architecture Ben Hutchings
2018-07-26 10:20 ` [PATCH 03/12] builddeb: Drop check for 32-bit s390 Ben Hutchings
2018-07-26 10:21 ` [PATCH 04/12] builddeb: Introduce functions to simplify kconfig tests in set_debarch Ben Hutchings
2018-07-26 10:21 ` [PATCH 05/12] builddeb: Add automatic support for ppc64 and powerpcspe architectures Ben Hutchings
2018-07-26 10:21 ` [PATCH 06/12] builddeb: Add automatic support for mips64el architecture Ben Hutchings
2018-07-26 10:22 ` [PATCH 07/12] builddeb: Add automatic support for mips{,64}r6{,el} architectures Ben Hutchings
2018-07-26 10:22 ` [PATCH 08/12] builddeb: Add automatic support for sparc64 architecture Ben Hutchings
2018-07-26 10:22 ` [PATCH 09/12] builddeb: Add automatic support for or1k architecture Ben Hutchings
2018-07-26 10:22 ` [PATCH 10/12] builddeb: Add automatic support for m68k architecture Ben Hutchings
2018-07-26 10:22 ` [PATCH 11/12] builddeb: Add automatic support for riscv* architectures Ben Hutchings
2018-07-26 10:22 ` [PATCH 12/12] builddeb: Add automatic support for sh{3,4}{,eb} architectures Ben Hutchings
2018-08-01 23:10 ` Masahiro Yamada [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='CAK7LNAS0hZDKQmP0aLCM9j-SiWgrmGW=jP4g_x+TqGBOmnPU1w@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kbuild@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.