From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Paul Burton <paul.burton@imgtec.com>, linux-mips@linux-mips.org
Cc: Ralf Baechle <ralf@linux-mips.org>, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 1/6] kbuild: Keep device tree tables though dead code elimination
Date: Fri, 21 Oct 2016 12:33:14 +0300 [thread overview]
Message-ID: <a4baa8e5-a2e1-9020-dd81-a064e1f7bb81@cogentembedded.com> (raw)
In-Reply-To: <20161020202705.3783-2-paul.burton@imgtec.com>
Hello.
s/though/through/ in the subject.
MBR, Sergei
next prev parent reply other threads:[~2016-10-21 9:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:26 [PATCH 0/6] MIPS: Use thin archives & dead code elimination Paul Burton
2016-10-20 20:26 ` Paul Burton
2016-10-20 20:27 ` [PATCH 1/6] kbuild: Keep device tree tables though " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-21 9:33 ` Sergei Shtylyov [this message]
2016-10-20 20:27 ` [PATCH 2/6] kbuild: Keep .init.setup section through " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 3/6] kbuild: Keep PCI fixups " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 4/6] kbuild: Keep earlycon table " Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-20 20:27 ` [PATCH 5/6] MIPS: Ensure bss section ends on a long-aligned address Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-11-04 8:46 ` Marcin Nowakowski
2016-11-04 8:46 ` Marcin Nowakowski
2016-10-20 20:27 ` [PATCH 6/6] MIPS: Use thin archives & dead code elimination Paul Burton
2016-10-20 20:27 ` Paul Burton
2016-10-21 0:51 ` [PATCH 0/6] " Nicholas Piggin
2016-10-21 0:51 ` Nicholas Piggin
2016-10-21 7:45 ` Paul Burton
2016-10-21 7:45 ` Paul Burton
2016-10-21 8:47 ` Nicholas Piggin
2016-10-21 8:47 ` Nicholas Piggin
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=a4baa8e5-a2e1-9020-dd81-a064e1f7bb81@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-mips@linux-mips.org \
--cc=npiggin@gmail.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.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).