From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PULL REQUEST] i2c-mux for 4.14-rc1
Date: Mon, 28 Aug 2017 17:15:28 +0200 [thread overview]
Message-ID: <20170828151528.GB10688@katana> (raw)
In-Reply-To: <7628db77-325b-7be9-cd01-32a29d2cb83a@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
> Hmm, it's not pushed out yet. No rush on my account, I'm probably just
> impatient. But (just so that I have something to go on) what is the
> ball-park time between your 'apply' message and the following push?
Usually the same evening. This time it got delayed/interrupted because
patchwork was failing for me yesterday and so my workflow was a bit ...
unusual. But it is back to work now, yay!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-08-28 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 7:00 [PULL REQUEST] i2c-mux for 4.14-rc1 Peter Rosin
2017-08-27 13:27 ` Wolfram Sang
2017-08-28 15:03 ` Peter Rosin
2017-08-28 15:15 ` Wolfram Sang [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=20170828151528.GB10688@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@axentia.se \
/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).