From: Mark Brown <broonie@kernel.org>
To: Kosta Zertsekel <zertsekel@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
"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: Tue, 28 Aug 2018 21:12:05 +0100 [thread overview]
Message-ID: <20180828201205.GR2414@sirena.org.uk> (raw)
In-Reply-To: <CADxo8W+JMKJvf8LUdH7_2EXqfi8KvrSPAYa=CZV1eMq2VrQ5rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On Fri, Aug 24, 2018 at 11:55:18PM +0300, Kosta Zertsekel wrote:
> Guys,
>
> Any additional comments?
> Or the patch is ready to be merged?
>
> Thanks,
> --- Kosta Z.
Please don't send content free pings and please allow a reasonable time
for review. People get busy, go on holiday, attend conferences and so
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review. If there have been
review comments then people may be waiting for those to be addressed.
Sending content free pings just adds to the mail volume (if they are
seen at all) and if something has gone wrong you'll have to resend the
patches anyway.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-08-28 20:12 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
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 [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=20180828201205.GR2414@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@lunn.ch \
--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 \
--cc=zertsekel@gmail.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).