public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: tpmdd-devel@lists.sourceforge.net,
	Matthias Leblanc <matthias.leblanc@gmail.com>
Cc: Mathias LEBLANC <Mathias.LEBLANC@st.com>,
	Kent Yoder <key@linux.vnet.ibm.com>,
	"Jean-Luc BLANC" <jean-luc.blanc@st.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mathias leblanc <mathias.lebanc@st.com>
Subject: Re: [tpmdd-devel] [PATCH 1/1] TPM: STMicroelectronics st33 driver SPI
Date: Thu, 11 Apr 2013 23:44:04 +0200	[thread overview]
Message-ID: <201304112344.04576.PeterHuewe@gmx.de> (raw)
In-Reply-To: <35286B1AE75A7C47BFF0870081A31B4B45A568E70B@SAFEX1MAIL4.st.com>

Hi Matthias,
Am Donnerstag, 11. April 2013, 10:58:59 schrieb Mathias LEBLANC:
> Hi Peter,
> 
> Yes, you have right, these error are generated by #ifndef
> __STM_ST33_TPM_SPI_H__ Just remove it and the #endif next the structure.
Yes, I know that - for the submission to be included this has to be changed by 
you.


> Did you have these warning when you have run checkpatch script?
You mean the sparse warnings I sent you?
I removed the superflous ifdef to compile it and then let sparse run against 
it.
The driver passes normal checkpatch check, unless you call it with -strict


Peter

  reply	other threads:[~2013-04-11 21:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 14:42 [PATCH 1/1] TPM: STMicroelectronics st33 driver SPI Matthias Leblanc
2013-04-10 20:32 ` [tpmdd-devel] " Peter Hüwe
2013-04-11  8:58   ` Mathias LEBLANC
2013-04-11 21:44     ` Peter Hüwe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-15 13:53 Matthias Leblanc
2013-05-15 22:29 ` [tpmdd-devel] " Peter Hüwe
2013-05-16  8:45   ` Mathias LEBLANC
2013-05-16 19:03     ` Peter Hüwe
2013-05-17 12:26       ` Mathias LEBLANC
2013-05-07 10:16 Matthias Leblanc
     [not found] ` <-7985513476024686594@unknownmsgid>
2013-05-10 15:06   ` [tpmdd-devel] " Kent Yoder
2013-05-13 15:30     ` Mathias LEBLANC
2013-05-13 15:56       ` Kent Yoder
2013-04-22  8:50 Mathias Leblanc
2013-04-22 15:26 ` [tpmdd-devel] " Kent Yoder
2013-04-22 16:32   ` Mathias LEBLANC
2013-04-22 18:31     ` Kent Yoder
2013-04-25 15:40       ` Mathias LEBLANC
2013-04-26 14:29         ` Kent Yoder
2013-04-28  1:16 ` Peter Hüwe
2013-04-29 14:15   ` Kent Yoder
2013-04-12  8:44 Matthias Leblanc
2013-04-17 21:31 ` [tpmdd-devel] " Kent Yoder
2013-04-19 16:06   ` Mathias LEBLANC
2013-03-25 15:08 Matthias Leblanc
2013-03-25 16:44 ` [tpmdd-devel] " Kent Yoder
2013-03-25 16:48   ` Mathias LEBLANC

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=201304112344.04576.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=Mathias.LEBLANC@st.com \
    --cc=jean-luc.blanc@st.com \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathias.lebanc@st.com \
    --cc=matthias.leblanc@gmail.com \
    --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