From: Thomas Tai <thomas.tai@oracle.com>
To: bhelgaas@google.com, rostedt@goodmis.org, thomas.tai@oracle.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
mr.nuke.me@gmail.com
Subject: [PATCH V3 0/1] PCI/AER: add pcie TLP header information in the tracepoint
Date: Tue, 8 May 2018 19:04:55 -0400 [thread overview]
Message-ID: <1525820696-31967-1-git-send-email-thomas.tai@oracle.com> (raw)
Hi Bjorn and Steven,
Would you kindly review the patch for me? following are the
changes details. Please feel free to comment.
Change log since last version:
V3:
1. use u8 for boolean variable
2. check tlp_header_valid before accessing tlp_header
3. replace sizeof(unsigned int) with 4
4. change the variable name buf to tlp_header for better reading
5. avoid extra dereference
Thank you,
Thomas
next reply other threads:[~2018-05-08 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 23:04 Thomas Tai [this message]
2018-05-08 23:04 ` [PATCH V3 1/1] PCI/AER: add pcie TLP header information in the tracepoint Thomas Tai
2018-05-09 12:38 ` Steven Rostedt
2018-05-09 14:12 ` Thomas Tai
2018-05-10 13:37 ` Bjorn Helgaas
2018-05-10 13:47 ` Thomas Tai
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=1525820696-31967-1-git-send-email-thomas.tai@oracle.com \
--to=thomas.tai@oracle.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=rostedt@goodmis.org \
/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).