From: Ralf Baechle <ralf@linux-mips.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: dbrownell@users.sourceforge.net,
Jassi Brar <jassi.brar@samsung.com>,
jassi brar <jassisinghbrar@gmail.com>,
patchwork <patchwork@ozlabs.org>,
spi-devel-general@lists.sourceforge.net,
Jeremy Kerr <jeremy.kerr@canonical.com>,
ben@trinity.fluff.org
Subject: Re: [PATCH 4/6] SPI: S3C64XX: Check before mem-region release
Date: Fri, 22 Jan 2010 15:51:19 +0100 [thread overview]
Message-ID: <20100122145119.GA6828@linux-mips.org> (raw)
In-Reply-To: <fa686aa41001210700p4d06ff45h4db23c9ea03d6ffb@mail.gmail.com>
On Thu, Jan 21, 2010 at 08:00:11AM -0700, Grant Likely wrote:
> Since I review patches on patchwork, I don't have an easy link between
> what I'm picking up and my email client. Only when I need to comment
> on something will I actually go and find the thread in my mailer. So
> it is considerably less efficient for me to go and reply to every
> patch submission.
I use the message-id: header from the patchwork page to find a patch in
my mailfolder. That's not too time consuming and has the advantage that
all my mail replies are also in my mail folders. I'm using mutt; I
know some mail clients mail readers make searching for a message ID a
pain.
Ralf
next prev parent reply other threads:[~2010-01-22 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 9:50 [PATCH 1/6] SPI: S3C64XX: Rename s3c64xx_spi_cntrlr_info jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-1-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 9:50 ` [PATCH 2/6] SPI: S3C64XX: Differentiate ip and rate clock jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-2-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 9:50 ` [PATCH 3/6] SPI: S3C64XX: Move src_clk to local driver data jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-3-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 9:50 ` [PATCH 4/6] SPI: S3C64XX: Check before mem-region release jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-4-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 9:50 ` [PATCH 5/6] SPI: S3C64XX: Include moved header jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-5-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 9:50 ` [PATCH 6/6] SPI: S3C64XX: Add new parameter to cs callback jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1263808215-16544-6-git-send-email-jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-18 18:15 ` Grant Likely
[not found] ` <fa686aa41001181015g6b3d35fdy8ee0f5134a8ca1a5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 23:49 ` jassi brar
2010-01-18 18:13 ` [PATCH 5/6] SPI: S3C64XX: Include moved header Grant Likely
[not found] ` <fa686aa41001181013i62142f3fs5c387a406f3b7d59-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 23:46 ` jassi brar
2010-01-18 18:12 ` [PATCH 4/6] SPI: S3C64XX: Check before mem-region release Grant Likely
[not found] ` <fa686aa41001181012s57c0e863s6b9b6b2724514a9f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 23:42 ` jassi brar
[not found] ` <1b68c6791001181542p618a8d47n45a120e51cfed1f1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 2:32 ` Grant Likely
[not found] ` <fa686aa41001181832r3d2462f6y87649244b8afc5f2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-19 9:52 ` jassi brar
[not found] ` <1b68c6791001190152m652fd117k468893144af8dcfe-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 1:35 ` jassi brar
[not found] ` <1b68c6791001201735w3060c54blfa85b547917727c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 1:46 ` jassi brar
[not found] ` <1b68c6791001201746p313234bbkdf5fe5db0dcecd9f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 2:55 ` Grant Likely
[not found] ` <fa686aa41001201855m5c054d90nb3652a5b0d3ffd86-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 3:06 ` jassi brar
[not found] ` <1b68c6791001201906r45c52f71h7f5ea396e91ef3b8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-21 15:00 ` Grant Likely
2010-01-21 15:10 ` Carl-Daniel Hailfinger
2010-01-22 14:51 ` Ralf Baechle [this message]
2010-01-18 17:58 ` [PATCH 2/6] SPI: S3C64XX: Differentiate ip and rate clock Grant Likely
[not found] ` <fa686aa41001180958l15df3a9dyfa5869b6f53c8fcb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-18 23:40 ` jassi brar
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=20100122145119.GA6828@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ben@trinity.fluff.org \
--cc=dbrownell@users.sourceforge.net \
--cc=grant.likely@secretlab.ca \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.com \
--cc=jeremy.kerr@canonical.com \
--cc=patchwork@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).