From: Mark Brown <broonie@kernel.org>
To: Simon Glass <sjg@chromium.org>
Cc: Rajeshwari S Shinde <rajeshwari.s@samsung.com>,
linux-samsung-soc@vger.kernel.org, linux-spi@vger.kernel.org,
ALIM AKHTAR <alim.akhtar@samsung.com>,
Doug Anderson <dianders@google.com>,
t.figa@samsung.com
Subject: Re: [PATCH V4] spi: s3c64xx: Enable Word transfer
Date: Sat, 19 Oct 2013 21:04:47 +0100 [thread overview]
Message-ID: <20131019200447.GF2443@sirena.org.uk> (raw)
In-Reply-To: <CAPnjgZ1A335KstnpTRwpxEbBArtqh1sYSPQJBw6LX5zUeptpfA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Sat, Oct 19, 2013 at 10:58:47AM -0600, Simon Glass wrote:
> If it helps, patman (tools/patman in U-Boot tree) will strip this
> automatically (along with other Gerrit and Chrome OS stuff), run checkpatch
> and Doug has added features to automatically cc the relevant maintainers
> for Linux. I got sick of trying to remember to do all these steps.
Watch out for the automatic identification of MAINTAINERS though - you
do need to pay attention to what gets set and check it, get_maintainers
isn't 100% reliable. You should check what it does and make sure you
understand why each person there is getting CCed.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-19 20:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 5:32 [PATCH V4] spi: s3c64xx: Enable Word transfer Rajeshwari S Shinde
[not found] ` <1382074356-28430-1-git-send-email-rajeshwari.s-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-10-19 16:25 ` Mark Brown
[not found] ` <CAPnjgZ1A335KstnpTRwpxEbBArtqh1sYSPQJBw6LX5zUeptpfA@mail.gmail.com>
2013-10-19 20:04 ` Mark Brown [this message]
2013-10-29 10:59 ` Rajeshwari Birje
[not found] ` <CAPs=JDeOqkJT32quBH1tF9FtFUOt=CHP7m6ZqzhfASM2uPj-dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-29 11:29 ` Rajeshwari Birje
[not found] ` <CAPs=JDdzvnM5BzgRLhLsJrdwcVSwxd6x8_kFz0EvB=OjFfVszw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-29 16:39 ` Mark Brown
[not found] ` <20131029163926.GA6776-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-30 6:22 ` Rajeshwari Birje
[not found] ` <CAPs=JDeDbevjOtMH0y+9aVSbNSV4zmEQxWygtB-f69XzooSinQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-30 17:00 ` Mark Brown
2013-10-30 17:06 ` Tomasz Figa
2013-10-31 10:47 ` Rajeshwari Birje
2013-10-31 12:37 ` Tomasz Figa
2013-11-06 4:53 ` Rajeshwari Birje
2013-11-06 8:21 ` Mark Brown
[not found] ` <20131106082141.GA11602-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-07 9:22 ` Rajeshwari Birje
[not found] ` <CAPs=JDctq1yRbuwnFH40dnQJJHF0C_D1p3iVokSPusPXA27Qeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-07 9:39 ` Tomasz Figa
2013-11-07 9:59 ` Lukasz Czerwinski
2013-11-08 11:05 ` Mark Brown
2013-11-10 17:26 ` Tomasz Figa
2013-11-13 8:28 ` Andrzej Hajda
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=20131019200447.GF2443@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=dianders@google.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rajeshwari.s@samsung.com \
--cc=sjg@chromium.org \
--cc=t.figa@samsung.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.