public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Ashok Raj <ashok.raj@intel.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	Gayatri Kammela <gayatri.kammela@intel.com>,
	Ravi V Shankar <ravi.v.shankar@intel.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH v5 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping
Date: Thu, 28 Dec 2017 10:54:40 +0200	[thread overview]
Message-ID: <1514451280.7000.310.camel@linux.intel.com> (raw)
In-Reply-To: <1513902760-45605-6-git-send-email-sohil.mehta@intel.com>

On Thu, 2017-12-21 at 16:32 -0800, Sohil Mehta wrote:

> +		seq_puts(m, "\n");

seq_putc()

> +		seq_puts(m, "\n");

Ditto.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2017-12-28  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  0:32 [PATCH v5 0/5] Add Intel IOMMU debugfs support Sohil Mehta
2017-12-22  0:32 ` [PATCH v5 1/5] iommu/vt-d: Add debugfs support for Intel IOMMU internals Sohil Mehta
2017-12-22  0:32 ` [PATCH v5 2/5] iommu/vt-d: Add debugfs support to show context internals Sohil Mehta
2017-12-28  8:51   ` Andy Shevchenko
2018-01-02 21:01     ` Kammela, Gayatri
2017-12-22  0:32 ` [PATCH v5 3/5] iommu/vt-d: Add debugfs support to show register contents Sohil Mehta
2017-12-22  0:32 ` [PATCH v5 4/5] iommu/vt-d: Add debugfs support to show Pasid table contents Sohil Mehta
2017-12-22  0:32 ` [PATCH v5 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping Sohil Mehta
2017-12-28  8:54   ` Andy Shevchenko [this message]

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=1514451280.7000.310.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=gayatri.kammela@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=sohil.mehta@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