From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-crypto@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Benjamin Gilbert <bgilbert@cs.cmu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/19] crypto: proc - Fix checkpatch errors
Date: Sat, 20 Feb 2010 11:26:46 +0100 [thread overview]
Message-ID: <2d460de71002200226w5fa27d85maa3fa75e1dca8fdd@mail.gmail.com> (raw)
In-Reply-To: <20100220024814.GA32053@gondor.apana.org.au>
On Sat, Feb 20, 2010 at 03:48, Herbert Xu <herbert@gondor.apana.org.au> wrote:
>> In this case, please hold seed, tcrypt, wp512 & xcbc. I will
>> refactor them.
>
> OK.
Another workflow question:
Does LKML as a whole prefer rebased patches, patches on top of the
old one or does not one care as long as it's clear what to apply in what
order?
Or does everyone have a different opionion, in which case: What is
yours?
> Thanks for checking.
No need to thank me. You decide what goes in and I accept that.
I signed up to weworking stuff until it suits the relevant maintainer
before I cloned the repo.
Richard
next prev parent reply other threads:[~2010-02-20 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 0:22 Richard Hartmann
2010-02-19 1:48 ` Eric W. Biederman
2010-02-19 10:10 ` Richard Hartmann
2010-02-19 12:17 ` Herbert Xu
2010-02-19 16:35 ` Richard Hartmann
2010-02-20 0:46 ` Herbert Xu
2010-02-20 1:59 ` Richard Hartmann
2010-02-20 2:48 ` Herbert Xu
2010-02-20 10:26 ` Richard Hartmann [this message]
2010-02-20 13:12 ` Herbert Xu
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=2d460de71002200226w5fa27d85maa3fa75e1dca8fdd@mail.gmail.com \
--to=richih.mailinglist@gmail.com \
--cc=bgilbert@cs.cmu.edu \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=herbert@gondor.apana.org.au \
--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
all inboxes | Powered by JetHome®