From: Stephen Rothwell <sfr@canb.auug.org.au>
To: dwalker@fifo99.com
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: commits in the cisco tree
Date: Tue, 2 Oct 2018 04:12:31 +1000 [thread overview]
Message-ID: <20181002041231.01ce209b@canb.auug.org.au> (raw)
In-Reply-To: <20181001144257.GA13523@fifo99.com>
[-- Attachment #1: Type: text/plain, Size: 200 bytes --]
Hi Daniel,
On Mon, 1 Oct 2018 07:42:57 -0700 dwalker@fifo99.com wrote:
>
> Is this just an alert , or are you not merging for these reasons ?
Just an alert.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-10-01 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 1:24 linux-next: commits in the cisco tree Stephen Rothwell
2018-10-01 14:42 ` dwalker
2018-10-01 18:12 ` Stephen Rothwell [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=20181002041231.01ce209b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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