From: Anton Saraev <antonysaraev@gmail.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Jake Edge <jake@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH 0/3] staging/skein: more cleanup
Date: Sat, 24 May 2014 18:50:47 +0400 [thread overview]
Message-ID: <20140524145046.GA1844@Ruffial> (raw)
In-Reply-To: <20140522170441.GW8664@titan.lakedaemon.net>
On Thu, May 22, 2014 at 01:04:41PM -0400, Jason Cooper wrote:
> I do not, I'm unsure if Anton has anything pending capable of
> upstreaming.
I have two simple patches. But I don't know is it necessary to send
this patches. First is export of functions in *api.c files.
But it is trivial part of api cleanup. Second is fixing of remaining
uppercase X in skein_block.c. But this variables lie on SKEIN_DEBUG
compile path and maybe will be completely removed (or we need add
some output in the appropriate functions).
prev parent reply other threads:[~2014-05-24 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 13:56 [PATCH 0/3] staging/skein: more cleanup Jake Edge
2014-05-20 13:58 ` [PATCH 1/3] staging/skein: move all threefish block functions to one file Jake Edge
2014-05-20 14:00 ` [PATCH 2/3] staging/skein: comment typos Jake Edge
2014-05-20 14:02 ` [PATCH 3/3] staging/skein: variable/member name cleanup Jake Edge
2014-05-20 14:47 ` [PATCH 0/3] staging/skein: more cleanup Jason Cooper
2014-05-20 16:24 ` Jake Edge
2014-05-20 17:47 ` Jason Cooper
2014-05-20 21:52 ` Anton Saraev
2014-05-22 16:52 ` Jake Edge
2014-05-22 17:04 ` Jason Cooper
2014-05-24 14:50 ` Anton Saraev [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=20140524145046.GA1844@Ruffial \
--to=antonysaraev@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jake@lwn.net \
--cc=jason@lakedaemon.net \
--cc=joe@perches.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.