From: Peter Huewe <PeterHuewe@gmx.de>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Peter.Huewe@infineon.com, key@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [PATCH] TPM: Switch to __packed instead of __attribute__((packed))
Date: Wed, 21 Nov 2012 23:50:24 +0100 [thread overview]
Message-ID: <201211212350.24836.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20121121205645.GB15285@obsidianresearch.com>
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>
Thanks,
Peter
next prev parent reply other threads:[~2012-11-22 21:06 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 [this message]
2012-11-26 20:23 ` Kent Yoder
2012-11-26 20:30 ` Jason Gunthorpe
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=201211212350.24836.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=Peter.Huewe@infineon.com \
--cc=jgunthorpe@obsidianresearch.com \
--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;
as well as URLs for NNTP newsgroup(s).