mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
	james_p_freyensee@linux.intel.com, christophe.guerard@intel.com
Subject: 3rd request for review & addition of PTI/n_trace implementation into kernel
Date: Tue, 19 Apr 2011 15:58:05 -0700	[thread overview]
Message-ID: <1303253889-10074-1-git-send-email-james_p_freyensee@linux.intel.com> (raw)
In-Reply-To: <james_p_freyensee@linux.intel.com>

Apologies for a long delay between submission attempts- this is the 3rd request
for review and acceptance into the mainline kernel for the Intel-Atom
implementation of the MIPI P1149.7 compact JTAG
standard for mobile devices.  Complete documentation and background
has been provided in PATCH 02/12, "Kernel documentation for the PTI
feature".  PATCH 01/12 is a kernel fix to allow the PTI driver
to compile modularly; this is a fix Greg KH, Alan Cox, and Arjan
van de Ven and I talked about a while ago.  It's not techincally
related to PTI, but it is it's own separate patch so it can be
applied independent of any possible problems with the PTI submission.

Changes/fixes from last review include:
-lock acquire and release same ordering in n_tracesink and n_tracerouter
-variable renaming in pti.c
-elimination of one variable not used in pti.c
-patch groups submissions in logical, independent chunks instead one
 file per patch.
-use of linux-next instead of linux-stable for patch base
-Kconfig descriptions appearing in patch descriptions for
 pti and n_tracesink/n_tracerouter, as requested.

Thanks for your help and time. Regards,
J Freyensee

From: james_p_freyensee@linux.intel.com
Subject: 3rd request for review & addition of PTI/n_trace implementation into kernel
In-Reply-To: james_p_freyensee@linux.intel.com


                 reply	other threads:[~2011-04-19 22:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1303253889-10074-1-git-send-email-james_p_freyensee@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    --cc=christophe.guerard@intel.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suhail.ahmed@intel.com \
    /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