From: Mark Brown <broonie@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-spi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
hartleys@visionengravers.com, mika.westerberg@iki.fi,
Nathan Chancellor <natechancellor@gmail.com>
Subject: Re: [PATCH] spi: spi-ep93xx: Change dir type in ep93xx_spi_dma_{finish,prepare}
Date: Fri, 5 Oct 2018 12:15:31 +0100 [thread overview]
Message-ID: <20181005111531.GA6266@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOd=bZWsgggLMODN0OPSu=c=pQZsREvTtNcUn+arEEVJQjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Thu, Oct 04, 2018 at 09:41:20AM -0700, Nick Desaulniers wrote:
> On Thu, Oct 4, 2018 at 9:04 AM Nathan Chancellor
> > On Thu, Oct 04, 2018 at 11:32:47AM +0100, Mark Brown wrote:
> > > Please remember to CC driver maintainers and authors on patch
> > > submissions so they can review things, copying in Hartley and Mika.
> > Thank you for that, I usually just rely on get_maintainer.pl but I'll be
> If get_maintainer.pl doesn't cc the right person, does that signal
> that the MAINTAINERS file has some omissions?
It can do but there's always cases where it misses people - someone
working very actively on a bit of code for the short term for example.
Especially with drivers if you're only seeing subsystem maintainers then
it's worth checking. The --git option helps a lot here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-05 11:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 2:39 [PATCH] spi: spi-ep93xx: Change dir type in ep93xx_spi_dma_{finish,prepare} Nathan Chancellor
2018-10-04 2:40 ` [PATCH v2] " Nathan Chancellor
2018-10-04 21:32 ` Nick Desaulniers
2018-10-04 21:47 ` Nathan Chancellor
2018-10-04 23:12 ` Nick Desaulniers
2018-10-05 19:25 ` [PATCH v3] spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare} Nathan Chancellor
2018-10-05 20:41 ` Nick Desaulniers
2018-10-05 20:46 ` Nathan Chancellor
2018-10-08 7:52 ` Mika Westerberg
2018-10-08 18:08 ` [PATCH v4] " Nathan Chancellor
2018-10-08 18:14 ` Nick Desaulniers
2018-10-08 18:53 ` Mika Westerberg
2018-10-08 23:34 ` Applied "spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare}" to the spi tree Mark Brown
2018-10-08 23:34 ` Mark Brown
2018-10-04 10:32 ` [PATCH] spi: spi-ep93xx: Change dir type in ep93xx_spi_dma_{finish,prepare} Mark Brown
2018-10-04 16:04 ` Nathan Chancellor
2018-10-04 16:41 ` Nick Desaulniers
2018-10-05 11:15 ` Mark Brown [this message]
2018-10-05 8:28 ` Mika Westerberg
2018-10-05 8:52 ` Nathan Chancellor
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=20181005111531.GA6266@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@iki.fi \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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 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.