From: Javier Martinez Canillas <javier@dowhile0.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Doug Anderson" <dianders@chromium.org>,
"Jaehoon Chung" <jh80.chung@samsung.com>,
"Seungwon Jeon" <tgih.jun@samsung.com>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Sonny Rao" <sonnyrao@chromium.org>,
"Andrew Bresticker" <abrestic@chromium.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
"H Hartley Sweeten" <hsweeten@visionengravers.com>,
"Tony Lindgren" <tony@atomide.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Wolfram Sang" <wsa@the-dreams.de>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chris Ball" <chris@printf.net>,
"Grégory Soutadé" <gsoutade@neotion.com>,
"Joe Perches" <joe@perches.com>, "Axel Lin" <axel.lin@ingics.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/4] Fixes for SDIO interrupts for dw_mmc
Date: Fri, 2 Jan 2015 11:28:48 +0100 [thread overview]
Message-ID: <CABxcv==1w1GAHNCaNnh+e-xaYo8xtuD8dywTseioosxT4GZOvg@mail.gmail.com> (raw)
In-Reply-To: <CAPDyKFqGW2NaN+5mUrpBWrhM5ZfUSx70-Yyk9qmNaC1ft_ibpw@mail.gmail.com>
Hello Ulf,
On Tue, Dec 30, 2014 at 11:29 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On 19 December 2014 at 20:02, Doug Anderson <dianders@chromium.org> wrote:
>>
>>> It was a bit hard to follow the
>>> updated the revisions, please don't send patches "in-reply-to" for
>>> future sets.
>>
>> Very strange. I didn't send out anything in-reply-to other than what
>> git-send-email usually does. I believe I had:
>>
>> [0] - no in reply to.
>> [1] - in reply to [0]
>> [2] - in reply to [0]
>> [3] - in reply to [0]
>> [4] - in reply to [0]
>
> That's good. As long as there are no in-reply to previous versions of
> patches/patchsets.
>
> I am using gmails web-based client so it could very well be that it
> does some magic, which I am not yet aware of.
>
I think that you were confused because Gmail's "conversation view"
groups emails in a thread not by the email subject but by the email
body.
So if a new revision of a series is sent and a patch did not change
from the previous version, Gmail will add it to the old patch thread
since the body is basically the same even when a version is present in
the subject (e.g: PATCH v2 foo).
I found that annoying as well so I disabled conversation view going to
Gmail's settings -> General -> Conversation view off
Hope it helps.
Best regards,
Javier
next prev parent reply other threads:[~2015-01-02 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 23:42 [PATCH v5 0/4] Fixes for SDIO interrupts for dw_mmc Doug Anderson
2014-12-02 23:42 ` [PATCH v5 2/4] mmc: core: Support the optional init_card() callback for MMC and SD Doug Anderson
2014-12-02 23:42 ` [PATCH v5 3/4] mmc: dw_mmc: Cleanup disable of low power mode w/ SDIO interrupts Doug Anderson
2014-12-03 0:17 ` Jaehoon Chung
2014-12-03 0:36 ` Doug Anderson
2014-12-03 1:06 ` Jaehoon Chung
2014-12-03 1:12 ` Doug Anderson
2014-12-03 1:19 ` Jaehoon Chung
2014-12-02 23:42 ` [PATCH v5 4/4] mmc: dw_mmc: Protect read-modify-write of INTMASK with a lock Doug Anderson
2014-12-19 10:17 ` [PATCH v5 0/4] Fixes for SDIO interrupts for dw_mmc Ulf Hansson
2014-12-19 19:02 ` Doug Anderson
2014-12-30 10:29 ` Ulf Hansson
2015-01-02 10:28 ` Javier Martinez Canillas [this message]
2015-01-02 17:06 ` Doug Anderson
2015-01-02 17:11 ` Tony Lindgren
2015-01-03 9:31 ` Ulf Hansson
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='CABxcv==1w1GAHNCaNnh+e-xaYo8xtuD8dywTseioosxT4GZOvg@mail.gmail.com' \
--to=javier@dowhile0.org \
--cc=abrestic@chromium.org \
--cc=alim.akhtar@samsung.com \
--cc=axel.lin@ingics.com \
--cc=chris@printf.net \
--cc=dianders@chromium.org \
--cc=gsoutade@neotion.com \
--cc=heiko@sntech.de \
--cc=hsweeten@visionengravers.com \
--cc=jh80.chung@samsung.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=sonnyrao@chromium.org \
--cc=tgih.jun@samsung.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa@the-dreams.de \
/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).