From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: [RFC/PATCH v2] ftrace: Reduce size of function graph entries
Date: Tue, 28 Jun 2016 23:22:31 -0400 [thread overview]
Message-ID: <20160628232231.54549d29@gandalf.local.home> (raw)
In-Reply-To: <20160629023837.GD1628@sejong>
On Wed, 29 Jun 2016 11:38:37 +0900
Namhyung Kim <namhyung@kernel.org> wrote:
> Ok then, I'll change it to use 'packed' only in v3.
>
I would add a comment that the structure is already packed and that the
"packed" attribute is just to remove the extra padding at the end of
the struct.
-- Steve
prev parent reply other threads:[~2016-06-29 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 5:30 [RFC/PATCH v2] ftrace: Reduce size of function graph entries Namhyung Kim
2016-06-28 23:32 ` Steven Rostedt
2016-06-28 23:32 ` Steven Rostedt
2016-06-29 1:32 ` Namhyung Kim
2016-06-29 1:57 ` Steven Rostedt
2016-06-29 2:38 ` Namhyung Kim
2016-06-29 3:22 ` Steven Rostedt [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=20160628232231.54549d29@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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 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).