From: Michal Simek <monstr@monstr.eu>
To: Mark Brown <broonie@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] spi: xilinx: Use standard num-cs binding
Date: Mon, 23 Feb 2015 11:22:02 +0100 [thread overview]
Message-ID: <54EAFF4A.1080605@monstr.eu> (raw)
In-Reply-To: <20150214053543.GL9110@finisterre.sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi Mark,
On 02/14/2015 06:35 AM, Mark Brown wrote:
> On Wed, Feb 11, 2015 at 12:07:20PM +0100, Michal Simek wrote:
>> 2015-01-16 13:55 GMT+01:00 Michal Simek <michal.simek@xilinx.com>:
>
>>> Use standard num-cs binding property and setup
>>> "xlnx,num-ss-bits" as deprecated.
>
>> Any update on this one?
>
> Don't send content free quoted pings, they're just adding to the e-mail
> volume and hence wasting people's time.
How do you want me to send ping on pending patches?
Just send them with RESEND prefix?
I just want to clarify this.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-23 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 12:55 [PATCH] spi: xilinx: Use standard num-cs binding Michal Simek
[not found] ` <67f3c196833c427a489ca2c530d08987a6b5ee2a.1421412912.git.michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
2015-02-12 9:45 ` Michal Simek
2015-03-08 19:00 ` Mark Brown
2015-03-27 10:55 ` Michal Simek
[not found] ` <2a81c738-f7e2-4387-b04c-05c9892ba8e4-reflc3kr++MPoeFrVf1fn+hlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
2015-03-27 17:53 ` Mark Brown
[not found] ` <20150327175318.GG1743-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-03-30 6:46 ` Michal Simek
[not found] ` <1bd88fda-314c-496a-ba8b-e9292f9c411b-neA4ZlFjCT3bHPOQ8RbMe2YJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-03-31 5:47 ` Mark Brown
2015-03-31 8:16 ` Michal Simek
[not found] ` <74214fc9-e5e4-42db-bd85-51ed02975388-reflc3kr++MPoeFrVf1fn+hlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
2015-03-31 11:16 ` Mark Brown
2015-03-31 11:25 ` Michal Simek
[not found] ` <98b110d7-f875-4bd5-98de-47641ac2134c-reflc3kr++MPoeFrVf1fn+hlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
2015-03-31 12:24 ` Mark Brown
[not found] ` <CAHTX3dJRGhwo7FW+VJxfEJmx-9FdjFN5EnxG0RRDfMOm3=VU4A@mail.gmail.com>
[not found] ` <CAHTX3dJRGhwo7FW+VJxfEJmx-9FdjFN5EnxG0RRDfMOm3=VU4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-14 5:35 ` Mark Brown
2015-02-23 10:22 ` Michal Simek [this message]
[not found] ` <54EAFF4A.1080605-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2015-02-24 14:52 ` Mark Brown
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=54EAFF4A.1080605@monstr.eu \
--to=monstr@monstr.eu \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=soren.brinkmann@xilinx.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).