From: Mark Brown <broonie@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-kernel@vger.kernel.org, andriy.shevchenko@linux.intel.com,
linux-mtd@lists.infradead.org, linuxarm@huawei.com,
linux-spi@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth
Date: Mon, 2 Mar 2020 12:22:20 +0000 [thread overview]
Message-ID: <20200302122220.GA4166@sirena.org.uk> (raw)
In-Reply-To: <07bb2213-5543-0ef0-9585-be83026c1199@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
On Mon, Mar 02, 2020 at 09:30:08AM +0000, John Garry wrote:
> Do you want me to do anything about the above superfluous newline?
Whatever you prefer, I don't really care either way.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: John Garry <john.garry-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: Sergei Shtylyov
<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth
Date: Mon, 2 Mar 2020 12:22:20 +0000 [thread overview]
Message-ID: <20200302122220.GA4166@sirena.org.uk> (raw)
In-Reply-To: <07bb2213-5543-0ef0-9585-be83026c1199-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 184 bytes --]
On Mon, Mar 02, 2020 at 09:30:08AM +0000, John Garry wrote:
> Do you want me to do anything about the above superfluous newline?
Whatever you prefer, I don't really care either way.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: John Garry <john.garry@huawei.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org, linux-mtd@lists.infradead.org,
andriy.shevchenko@linux.intel.com
Subject: Re: [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth
Date: Mon, 2 Mar 2020 12:22:20 +0000 [thread overview]
Message-ID: <20200302122220.GA4166@sirena.org.uk> (raw)
In-Reply-To: <07bb2213-5543-0ef0-9585-be83026c1199@huawei.com>
[-- Attachment #1.1: Type: text/plain, Size: 184 bytes --]
On Mon, Mar 02, 2020 at 09:30:08AM +0000, John Garry wrote:
> Do you want me to do anything about the above superfluous newline?
Whatever you prefer, I don't really care either way.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 144 bytes --]
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-03-02 12:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:18 [PATCH RFC 0/3] spi/HiSilicon v3xx: Support dual and quad mode through DMI quirks John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 15:18 ` [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 18:25 ` Applied "spi: Allow SPI controller override device buswidth" to the spi tree Mark Brown
2020-02-28 18:25 ` Mark Brown
2020-02-28 18:25 ` Mark Brown
2020-03-01 10:04 ` [PATCH RFC 1/3] spi: Allow SPI controller override device buswidth Sergei Shtylyov
2020-03-01 10:04 ` Sergei Shtylyov
2020-03-01 10:04 ` Sergei Shtylyov
2020-03-02 9:30 ` John Garry
2020-03-02 9:30 ` John Garry
2020-03-02 12:22 ` Mark Brown [this message]
2020-03-02 12:22 ` Mark Brown
2020-03-02 12:22 ` Mark Brown
2020-03-02 16:12 ` Geert Uytterhoeven
2020-03-02 16:12 ` Geert Uytterhoeven
2020-03-02 16:33 ` Mark Brown
2020-03-02 16:33 ` Mark Brown
2020-03-02 18:51 ` Geert Uytterhoeven
2020-03-02 18:51 ` Geert Uytterhoeven
2020-03-02 18:51 ` Geert Uytterhoeven
2020-03-03 9:42 ` John Garry
2020-03-03 9:42 ` John Garry
2020-03-03 9:42 ` John Garry
2020-03-03 12:43 ` Mark Brown
2020-03-03 12:43 ` Mark Brown
2020-03-03 12:43 ` Mark Brown
2020-02-28 15:18 ` [PATCH RFC 2/3] spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 18:25 ` Applied "spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes" to the spi tree Mark Brown
2020-02-28 18:25 ` Mark Brown
2020-02-28 18:25 ` Mark Brown
2020-02-28 15:18 ` [PATCH RFC 3/3] spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits John Garry
2020-02-28 15:18 ` John Garry
2020-02-28 16:20 ` Mark Brown
2020-02-28 16:20 ` Mark Brown
2020-02-28 16:20 ` Mark Brown
2020-02-28 17:17 ` John Garry
2020-02-28 17:17 ` John Garry
2020-02-28 17:17 ` John Garry
2020-02-28 18:25 ` Applied "spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits" to the spi tree Mark Brown
2020-02-28 18:25 ` Mark Brown
2020-02-28 18:25 ` 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=20200302122220.GA4166@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.