All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Stephen Brennan <stephen@brennan.io>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] staging: ccree: Fix lines longer than 80 characters
Date: Sat, 21 Oct 2017 10:48:21 +0300	[thread overview]
Message-ID: <CAOtvUMfzH86anJJ2JcsVdpX7wzfWh2PYNDUhA0JZ7SP+BfWYpw@mail.gmail.com> (raw)
In-Reply-To: <20171020195754.GA4913@pride.attlocal.net>

Hello Stephen,

Thank you for your patch! sorry for not responding to your first post.
I seem to have missed that
email completely.

The CryptoCell driver is currently in the staging process for
inclusion in the Linux kernel.
As such, patches such as these are discussed in the staging mailing
list and should include
also the staging tree maintainer.

TIP: if you run the scripts/get_maintainers.pl script on your patch it
will tell you exactly which
list and which people your patch needs to be addressed, so you don't
have to guess.

Also, you are missing a patch description. While it's rather trivial
in this case, it still needs to be written.

TIP: Run the scripts/checkpath.pl on your patch before sending it and
it will let you know what you are missing, if any :-)

Please keep sending patches :-)

Thanks,
Gilad


On Fri, Oct 20, 2017 at 10:57 PM, Stephen Brennan <stephen@brennan.io> wrote:
> Hello,
>
> Just bumping this patch. I know it's only a very trivial change that shuts
> up a checkpatch warning. Please let me know if I can do anything to help.
>
> Thanks,
> Stephen
>



-- 
Gilad Ben-Yossef
Chief Coffee Drinker

"If you take a class in large-scale robotics, can you end up in a
situation where the homework eats your dog?"
 -- Jean-Baptiste Queru

  reply	other threads:[~2017-10-21  7:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  4:27 [PATCH] staging: ccree: Fix lines longer than 80 characters Stephen Brennan
2017-10-20 19:57 ` Stephen Brennan
2017-10-21  7:48   ` Gilad Ben-Yossef [this message]
2017-10-23 15:00     ` Stephen Brennan
2017-10-24  8:54       ` Gilad Ben-Yossef
2017-10-23 14:53 Stephen Brennan
2017-10-23 14:53 ` Stephen Brennan
2017-10-24  3:02 ` Tobin C. Harding
2017-10-24  8:49   ` Gilad Ben-Yossef
2017-10-24  8:49     ` Gilad Ben-Yossef
2017-10-24  9:44     ` Tobin C. Harding
2017-10-24  9:55       ` Greg Kroah-Hartman
2017-10-25  6:52       ` Stephen Brennan
2017-10-25  9:46         ` Tobin C. Harding
2017-10-27  1:51 Stephen Brennan
2017-10-27  1:51 ` Stephen Brennan
2017-10-27  1:53 ` Stephen Brennan
2017-10-27  1:53   ` Stephen Brennan

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=CAOtvUMfzH86anJJ2JcsVdpX7wzfWh2PYNDUhA0JZ7SP+BfWYpw@mail.gmail.com \
    --to=gilad@benyossef.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=stephen@brennan.io \
    /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.