linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	devel@driverdev.osuosl.org,
	driverdev-devel@linuxdriverproject.org,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Ofir Drang <ofir.drang@arm.com>
Subject: Re: [PATCH 0/3] More code cleanups
Date: Mon, 6 Nov 2017 08:58:44 +0100	[thread overview]
Message-ID: <20171106075844.GA9470@kroah.com> (raw)
In-Reply-To: <CAOtvUMfZuQktTQFJXGRZgF-nO3AUWbzR44Z1pptUh-inYvcVbw@mail.gmail.com>

On Mon, Nov 06, 2017 at 09:41:09AM +0200, Gilad Ben-Yossef wrote:
> On Mon, Nov 6, 2017 at 9:38 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, Nov 06, 2017 at 06:55:49AM +0000, Gilad Ben-Yossef wrote:
> >> Additional code readability and simplification patches.
> >> These goes on top the previous patch set sent to the list.
> >
> > Please label your 0/X patches the same way your patches are, with the
> > prefix of the subsystem, otherwise they get dropped from my searches of
> > my inbox at times.
> >
> > For this one, it would be:
> >         [PATCH 0/3] staging: ccree: More code cleanups.
> >
> > thanks,
> 
> Oopss.., sorry.
> 
> Writing that subject line is almost the only thing not automated in
> my patch set sending process so of course I mangled it ...
> 
> Do you want to me to resend this patch series?

No, I'll handle it, thanks.

greg k-h

      reply	other threads:[~2017-11-06  7:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06  6:55 [PATCH 0/3] More code cleanups Gilad Ben-Yossef
2017-11-06  6:55 ` [PATCH 1/3] staging: ccree: simplify error handling logic Gilad Ben-Yossef
2017-11-06  6:55 ` [PATCH 2/3] staging: ccree: simplify registers access Gilad Ben-Yossef
2017-11-06  6:55 ` [PATCH 3/3] staging: ccree: simplify ioread/iowrite Gilad Ben-Yossef
2017-11-06  8:37   ` Tobin C. Harding
2017-11-06  8:59     ` Gilad Ben-Yossef
2017-11-06 15:46       ` Greg Kroah-Hartman
2017-11-06 20:24         ` Tobin C. Harding
2017-11-06  7:38 ` [PATCH 0/3] More code cleanups Greg Kroah-Hartman
2017-11-06  7:41   ` Gilad Ben-Yossef
2017-11-06  7:58     ` Greg Kroah-Hartman [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=20171106075844.GA9470@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gilad@benyossef.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ofir.drang@arm.com \
    /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).