From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Naga Sureshkumar Relli
<naga.sureshkumar.relli-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org,
punnaia-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org,
harinik-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Naga Sureshkumar Relli
<nagasure-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v2 3/3] spi: xilinx: Update devicetree bindings for spi-xilinx
Date: Mon, 30 May 2016 18:38:39 +0100 [thread overview]
Message-ID: <20160530173839.GA29837@sirena.org.uk> (raw)
In-Reply-To: <1464601627-5246-1-git-send-email-nagasure-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 376 bytes --]
On Mon, May 30, 2016 at 03:17:07PM +0530, Naga Sureshkumar Relli wrote:
> Update bindings for spi-xilinx.
> as per spi-bus.txt rename num-ss-bits to num-cs.
> and add fifo-size and bits-per-word properties.
This makes the new bindings backwards incompatible breaking existing
machine descriptions. It's fine to add new options but the driver
should accept the old options.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-05-30 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 9:47 [PATCH v2 3/3] spi: xilinx: Update devicetree bindings for spi-xilinx Naga Sureshkumar Relli
[not found] ` <1464601627-5246-1-git-send-email-nagasure-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2016-05-30 17:38 ` Mark Brown [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=20160530173839.GA29837@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=harinik-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=naga.sureshkumar.relli-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=nagasure-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=punnaia-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.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).