From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, Jules Irenge <jbi.octave@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/2] Lock warning cleanup
Date: Thu, 30 Apr 2020 15:41:14 +0100 [thread overview]
Message-ID: <20200430144114.GE4633@sirena.org.uk> (raw)
In-Reply-To: <158825658829.42351.8658305560393460400.b4-ty@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
On Thu, Apr 30, 2020 at 03:23:17PM +0100, Mark Brown wrote:
> [1/2] cxgb4: Add missing annotation for service_ofldq()
> commit: d7f27df50eea54fd00c26c5dda7bc12d2541e5e4
Sorry, I didn't register that this was part of a series when I
downloaded the mailbox - I'll drop that commit. When sending small
cleanups like this to unrelated subsystems putting them in a series, it
makes it look like there's dependencies. This is especially true if
you're not CCing the whole series to everyone, that's often a sign that
you can just separate the cleanups.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-04-30 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0/2>
2020-01-30 0:28 ` [PATCH 0/2] Lock warning clean up Jules Irenge
2020-01-30 0:29 ` [PATCH 1/2] fs_pin: Add missing annotation to pin_kill() declaration Jules Irenge
2020-01-30 0:30 ` [PATCH 2/2] rcu/nocb: Add missing annotation for rcu_nocb_bypass_unlock() Jules Irenge
2020-01-31 0:59 ` Boqun Feng
2020-01-31 4:42 ` Paul E. McKenney
2020-04-29 22:57 ` [PATCH 0/2] Lock warning cleanup Jules Irenge
2020-04-29 22:57 ` [PATCH 1/2] cxgb4: Add missing annotation for service_ofldq() Jules Irenge
2020-04-29 22:57 ` [PATCH 2/2] spi: atmel: Add missing annotation for atmel_spi_next_xfer_dma_submit() Jules Irenge
2020-04-30 14:23 ` [PATCH 0/2] Lock warning cleanup Mark Brown
2020-04-30 14:41 ` Mark Brown [this message]
[not found] ` <20200803122430.82364-1-jbi.octave@gmail.com>
2020-08-03 12:24 ` [PATCH 1/2] audit: change unnecessary globals into statics Jules Irenge
2020-08-03 12:24 ` [PATCH 2/2] audit: uninitialize variable audit_sig_sid Jules Irenge
2020-08-03 12:34 ` [RESEND PATCH 0/2] cleanups Jules Irenge
2020-08-03 12:34 ` [RESEND PATCH 1/2] audit: change unnecessary globals into statics Jules Irenge
2020-08-06 18:33 ` Paul Moore
2020-08-18 0:38 ` Paul Moore
2020-08-03 12:34 ` [RESEND PATCH 2/2] audit: uninitialize variable audit_sig_sid Jules Irenge
2020-08-06 18:35 ` Paul Moore
2020-08-18 0:38 ` Paul Moore
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=20200430144114.GE4633@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jbi.octave@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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