All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jake Edge <jake@lwn.net>
To: Jason Cooper <jason@lakedaemon.net>
Cc: 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>,
	Anton Saraev <antonysaraev@gmail.com>
Subject: Re: [PATCH 0/3] staging/skein: more cleanup
Date: Tue, 20 May 2014 10:24:11 -0600	[thread overview]
Message-ID: <20140520102411.413d565d@chukar.edge2.net> (raw)
In-Reply-To: <20140520144757.GA8664@titan.lakedaemon.net>

On Tue, 20 May 2014 10:47:57 -0400 Jason Cooper wrote:

> Do you have any other series pending for this driver?

No and I won't be doing anything else for the next couple of days --
some darn weekly edition to deal with :)

It seems like most of the straightforward stuff has been dealt with at
this point.  That rats nest of ifdefs in skein_block.c needs attention,
but some kind of tests are needed to ensure nothing breaks before
digging into that ...

jake

-- 
Jake Edge - LWN - jake@lwn.net - http://lwn.net

  reply	other threads:[~2014-05-20 16:24 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 [this message]
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

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=20140520102411.413d565d@chukar.edge2.net \
    --to=jake@lwn.net \
    --cc=antonysaraev@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --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.