From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Kent Yoder <key@linux.vnet.ibm.com>
Cc: Peter Huewe <PeterHuewe@gmx.de>,
Peter.Huewe@infineon.com, linux-kernel@vger.kernel.org,
tpmdd-devel@lists.sourceforge.net
Subject: Re: [PATCH] TPM: Switch to __packed instead of __attribute__((packed))
Date: Mon, 26 Nov 2012 13:30:19 -0700 [thread overview]
Message-ID: <20121126203019.GA18296@obsidianresearch.com> (raw)
In-Reply-To: <20121126202356.GC12737@ennui.austin.ibm.com>
On Mon, Nov 26, 2012 at 02:23:56PM -0600, Kent Yoder wrote:
> On Wed, Nov 21, 2012 at 11:50:24PM +0100, Peter Huewe wrote:
> > Am Mittwoch, 21. November 2012, 21:56:45 schrieb Jason Gunthorpe:
> > > This seems to be preferred these days.
> > >
> > > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
> >
> > Looks good to me
> > Reviewed-by: Peter Huewe <peterhuewe@gmx.de>
>
> Applied. I also rolled in an update to tpm_acpi.c to this commit:
>
> diff --git a/drivers/char/tpm/tpm_acpi.c b/drivers/char/tpm/tpm_acpi.c
> index 56051d0..64420b3 100644
> +++ b/drivers/char/tpm/tpm_acpi.c
> @@ -33,13 +33,13 @@ struct acpi_tcpa {
> u16 platform_class;
> union {
> struct client_hdr {
> - u32 log_max_len __attribute__ ((packed));
> - u64 log_start_addr __attribute__ ((packed));
> + u32 log_max_len __packed;
> + u64 log_start_addr __packed;
> } client;
> struct server_hdr {
> u16 reserved;
> - u64 log_max_len __attribute__ ((packed));
> - u64 log_start_addr __attribute__ ((packed));
> + u64 log_max_len __packed;
> + u64 log_start_addr __packed;
> } server;
> };
> };
Thanks, I looked at those as well, but I couldn't grok the
intent. What does __packed on a member even do??
Certainly client_hdr should be moved to the struct, maybe server_hdr
too?
Jason
prev parent reply other threads:[~2012-11-26 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 20:56 [PATCH] TPM: Switch to __packed instead of __attribute__((packed)) Jason Gunthorpe
2012-11-21 22:50 ` Peter Huewe
2012-11-26 20:23 ` Kent Yoder
2012-11-26 20:30 ` Jason Gunthorpe [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=20121126203019.GA18296@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Peter.Huewe@infineon.com \
--cc=PeterHuewe@gmx.de \
--cc=key@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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