From: Stephen Brennan <stephen@brennan.io>
To: Gilad Ben-Yossef <gilad@benyossef.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-crypto@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ccree: Fix lines longer than 80 characters
Date: Thu, 26 Oct 2017 18:53:12 -0700 [thread overview]
Message-ID: <20171027015312.GA6280@pride.cult> (raw)
In-Reply-To: <20171027015128.6170-1-stephen@brennan.io>
Apologies for the noise, this was the wrong patch. Please ignore this.
next prev parent reply other threads:[~2017-10-27 1:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 1:51 [PATCH] staging: ccree: Fix lines longer than 80 characters Stephen Brennan
2017-10-27 1:53 ` Stephen Brennan [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-23 14:53 Stephen Brennan
2017-10-24 3:02 ` Tobin C. Harding
2017-10-24 8:49 ` Gilad Ben-Yossef
2017-10-10 4:27 Stephen Brennan
2017-10-20 19:57 ` Stephen Brennan
2017-10-21 7:48 ` Gilad Ben-Yossef
2017-10-23 15:00 ` Stephen Brennan
2017-10-24 8:54 ` Gilad Ben-Yossef
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=20171027015312.GA6280@pride.cult \
--to=stephen@brennan.io \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gilad@benyossef.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).