public inbox for b43-dev@lists.infradead.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Nick Desaulniers <ndesaulniers@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	Alexander Potapenko <glider@google.com>,
	Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
	x86@kernel.org, drbd-dev@lists.linbit.com,
	linux-block@vger.kernel.org, b43-dev@lists.infradead.org,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-spi@vger.kernel.org,
	linux-mm@kvack.org, clang-built-linux@googlegroups.com
Subject: [PATCH v2 08/16] spi: davinci: Remove uninitialized_var() usage
Date: Thu, 2 Jul 2020 08:42:17 -0700	[thread overview]
Message-ID: <202007020839.545A571CA4@keescook> (raw)
In-Reply-To: <20200702152335.GJ4483@sirena.org.uk>

On Thu, Jul 02, 2020 at 04:23:35PM +0100, Mark Brown wrote:
> On Thu, Jul 02, 2020 at 08:21:40AM -0700, Kees Cook wrote:
> > On Wed, Jul 01, 2020 at 09:39:20PM +0100, Mark Brown wrote:
> 
> > > Please copy maintainers on patches :(
> 
> > Hi! Sorry about that; the CC list was giant, so I had opted for using
> > subsystem mailing lists where possible.
> 
> If you're going to err in a direction there I'd err in the direction of
> CCing the people not the list - I only saw this since I was looking for
> something else, I don't normally see stuff in the mailing list folder.

Yeah, I've gotten conflicting feedback on treewide changes:
- please CC me on only the one patch, I don't want to see everything else
- please CC me on the whole series, I want the full context for the change

I opted toward "CC me on this series", but then I get stuck when the CC
is giant. I think I may switch back to individual CCs for specific
patches, and point people to lore if they want greater context. (lore
didn't exist before...)

Thanks for the poke to make me reconsider this workflow. :)

-- 
Kees Cook

  reply	other threads:[~2020-07-02 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200620033007.1444705-1-keescook@chromium.org>
     [not found] ` <20200620033007.1444705-8-keescook@chromium.org>
2020-06-22  9:03   ` [PATCH v2 07/16] clk: st: Remove uninitialized_var() usage Stephen Boyd
     [not found] ` <20200620033007.1444705-10-keescook@chromium.org>
2020-06-22  9:03   ` [PATCH v2 09/16] clk: spear: " Stephen Boyd
     [not found] ` <CA+icZUWpHRR7ukyepiUH1dR3r4GMi-s2crfwR5vTszdt1SUTQw@mail.gmail.com>
     [not found]   ` <202006200854.B2D8F21@keescook>
2020-06-22  9:07     ` [PATCH v2 00/16] Remove uninitialized_var() macro Sedat Dilek
     [not found] ` <20200620033007.1444705-2-keescook@chromium.org>
2020-06-22 16:59   ` [PATCH v2 01/16] docs: deprecated.rst: Add uninitialized_var() Nick Desaulniers
     [not found] ` <20200620033007.1444705-11-keescook@chromium.org>
2020-06-22 17:22   ` [PATCH v2 10/16] KVM: PPC: Book3S PR: Remove uninitialized_var() usage Nick Desaulniers
     [not found] ` <20200620033007.1444705-17-keescook@chromium.org>
2020-06-22 17:27   ` [PATCH v2 13/16] mm/debug_vm_pgtable: " Nick Desaulniers
     [not found] ` <20200620033007.1444705-12-keescook@chromium.org>
2020-06-22 18:39   ` [PATCH v2 11/16] media: sur40: " Nick Desaulniers
     [not found] ` <20200620033007.1444705-9-keescook@chromium.org>
2020-07-01 20:39   ` [PATCH v2 08/16] spi: davinci: " Mark Brown
2020-07-02 15:21     ` Kees Cook
2020-07-02 15:23       ` Mark Brown
2020-07-02 15:42         ` Kees Cook [this message]
2020-07-02 16:23           ` Joe Perches
     [not found] ` <20200620033007.1444705-5-keescook@chromium.org>
2020-06-22 17:04   ` [PATCH v2 04/16] b43: " Nick Desaulniers
2020-06-22 21:04     ` Kees Cook
2020-06-23 18:29       ` Nick Desaulniers
2020-07-15 10:37   ` Kalle Valo

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=202007020839.545A571CA4@keescook \
    --to=keescook@chromium.org \
    --cc=apw@canonical.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=broonie@kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=glider@google.com \
    --cc=joe@perches.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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