mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Kent Yoder <key@linux.vnet.ibm.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Dan.Morav@nuvoton.com, linux-security-module@vger.kernel.org,
	mathias.leblanc@st.com
Subject: Re: [tpmdd-devel] TPM drivers' submission statuses
Date: Wed, 6 Feb 2013 10:16:07 -0700	[thread overview]
Message-ID: <20130206171607.GA28995@obsidianresearch.com> (raw)
In-Reply-To: <20130206154618.GA8296@ennui.austin.ibm.com>

On Wed, Feb 06, 2013 at 09:46:18AM -0600, Kent Yoder wrote:
> Hi,
> 
>   Occasionally I get a note from someone who's been pointed to me as
> having the latest version of a driver that isn't upstream.  The last
> submitted version of these drivers are usually sitting on the list,
> waiting on attention from their submitter. Hopefully I've added all the
> relevant folks on cc here, both submitters and reviewers.
> 
>   Here's the status of these drivers, from oldest to newest:
> 
> Nuvoton i2c:
>   Submitted to me off list. Review found issues. Needs resubmission
> to LKML. Last seen on the list:  https://lkml.org/lkml/2012/2/7/167

> Atmel i2c:
>   Submitted to tpmdd-devel for review. Waiting on a review from me.

FWIW, I have boards here with both of these chips and am very
interested in seeing support for these reach mainline.

I can look at and test the patches as well, if someone would send the
latest versions my way.

Regards,
Jason

           reply	other threads:[~2013-02-06 17:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130206154618.GA8296@ennui.austin.ibm.com>]

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=20130206171607.GA28995@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=Dan.Morav@nuvoton.com \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mathias.leblanc@st.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

Powered by JetHome