From: Kosta Zertsekel <zertsekel@gmail.com>
To: Mark Brown <broonie@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Jan Kundrát" <jan.kundrat@cesnet.cz>,
"Stefan Roese" <sr@denx.de>,
"Ken Wilson" <ken.wilson@opengear.com>
Subject: Re: [PATCH v4] spi: orion: cosmetics - alias long direct_access variables
Date: Fri, 24 Aug 2018 23:57:13 +0300 [thread overview]
Message-ID: <CADxo8WKvfKS+NEqPYj6SeR_F87Dub7OLPzEBbOESJ8L-=GEAWQ@mail.gmail.com> (raw)
In-Reply-To: <20180815190449.23738-1-zertsekel@gmail.com>
Guys,
Any additional comments?
Or the patch is ready to be merged?
Thanks,
--- Kosta Z.
next prev parent reply other threads:[~2018-08-24 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 19:04 [PATCH v4] spi: orion: cosmetics - alias long direct_access variables Kosta Zertsekel
2018-08-24 20:57 ` Kosta Zertsekel [this message]
2018-08-24 22:50 ` Jan Kundrát
[not found] ` <CADxo8W+JMKJvf8LUdH7_2EXqfi8KvrSPAYa=CZV1eMq2VrQ5rg@mail.gmail.com>
2018-08-24 21:01 ` Andrew Lunn
2018-08-28 20:12 ` 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='CADxo8WKvfKS+NEqPYj6SeR_F87Dub7OLPzEBbOESJ8L-=GEAWQ@mail.gmail.com' \
--to=zertsekel@gmail.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=jan.kundrat@cesnet.cz \
--cc=ken.wilson@opengear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sr@denx.de \
/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).