All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen@brennan.io>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH] staging: ccree: Fix lines longer than 80 characters
Date: Mon, 23 Oct 2017 08:00:06 -0700	[thread overview]
Message-ID: <20171023150006.GA8840@pride.attlocal.net> (raw)
In-Reply-To: <CAOtvUMfzH86anJJ2JcsVdpX7wzfWh2PYNDUhA0JZ7SP+BfWYpw@mail.gmail.com>

Hi Gilad,

Thanks for the quick reply, I really appreciate your taking time to help a
newbie get started. I've made the appropriate changes and re-submitted.

> 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.

When I ran this tool, it listed out quite a few mailing lists, including
linux-kernel@vger.kernel.org. Is it correct to simply address your patch to
the whole list output by the script? I omitted linux-kernel on my
resubmission, simply to avoid contributing to the heavy volume of that
list, given how trivial this patch is.

Thanks again!
Stephen

  reply	other threads:[~2017-10-23 14:59 UTC|newest]

Thread overview: 10+ 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
2017-10-23 15:00     ` Stephen Brennan [this message]
2017-10-24  8:54       ` Gilad Ben-Yossef
  -- strict thread matches above, loose matches on Subject: below --
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-27  1:51 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=20171023150006.GA8840@pride.attlocal.net \
    --to=stephen@brennan.io \
    --cc=gilad@benyossef.com \
    --cc=linux-crypto@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.