linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Purna Chandra Mandal <purna.mandal@microchip.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Joshua Henderson <digitalpeer@digitalpeer.com>,
	devicetree@vger.kernel.org, linux-mips@linux-mips.org,
	Kumar Gala <galak@codeaurora.org>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v5 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral
Date: Sat, 2 Apr 2016 09:35:06 -0700	[thread overview]
Message-ID: <20160402163506.GD2350@sirena.org.uk> (raw)
In-Reply-To: <1459509530-22716-1-git-send-email-purna.mandal@microchip.com>

[-- Attachment #1: Type: text/plain, Size: 236 bytes --]

On Fri, Apr 01, 2016 at 04:48:49PM +0530, Purna Chandra Mandal wrote:
> Document the devicetree bindings for the SPI peripheral found
> on Microchip PIC32 class devices.

Please use subject lines reflecting the style for the subsystem.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2016-04-02 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 11:18 [PATCH v5 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal
     [not found] ` <1459509530-22716-1-git-send-email-purna.mandal-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2016-04-01 11:18   ` [PATCH v5 2/2] spi: spi-pic32: Add PIC32 SPI master driver Purna Chandra Mandal
2016-04-02 16:35 ` Mark Brown [this message]
     [not found]   ` <20160402163506.GD2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-04-04 10:07     ` [PATCH v5 1/2] dt/bindings: Add bindings for PIC32 SPI peripheral Purna Chandra Mandal

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=20160402163506.GD2350@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=digitalpeer@digitalpeer.com \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=purna.mandal@microchip.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).