On Thu, 4 Dec 2014, Joe Perches wrote:
> On Thu, 2014-12-04 at 23:10 +0100, SF Markus Elfring wrote: > > The mppe_rekey() function contained a few update candidates. > > * Curly brackets were still used around a single function call "printk". > > * Unwanted space characters > > > > Let us improve these implementation details according to the current Linux > > coding style convention. > > trivia: > > > diff --git a/drivers/net/ppp/ppp_mppe.c b/drivers/net/ppp/ppp_mppe.c > [] > > @@ -172,9 +172,8 @@ static void mppe_rekey(struct ppp_mppe_state * state, > > int initial_key) > > setup_sg(sg_in, state->sha1_digest, state->keylen); > > setup_sg(sg_out, state->session_key, state->keylen); > > if (crypto_blkcipher_encrypt(&desc, sg_out, sg_in, > > - state->keylen) != 0) { > > - printk(KERN_WARNING "mppe_rekey: cipher_encrypt > > failed\n"); > > - } > > + state->keylen) != 0) > > + pr_warn("mppe_rekey: cipher_encrypt failed\n"); > > It's generally nicer to replace embedded function names > with "%s: ", __func__ > > pr_warn("%s: cipher_encrypt failed\n", __func__); Doing so may potentially allow some strings to be shared, thus saving a little space. Perhaps not in this case, though. julia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/