mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] USB: xHCI: Sync non-coherent DMA buffers
Date: Wed, 15 Apr 2015 11:11:47 +0200	[thread overview]
Message-ID: <1429089107.3365.11.camel@pengutronix.de> (raw)
In-Reply-To: <552D6AB3.2070505@gmail.com>

Am Dienstag, den 14.04.2015, 21:29 +0200 schrieb Sebastian Hesselbarth:
> On 14.04.2015 20:52, Sascha Hauer wrote:
> > On Mon, Apr 13, 2015 at 04:22:30PM +0200, Sebastian Hesselbarth wrote:
> >> ---
> >> Changelog:
> >> v1->v2:
> >> - balance dma_sync_single_foo() calls (Reported by Lucas Stach)
> >>
> >> Cc: barebox@lists.infradead.org
> >> Cc: Lucas Stach <dev@lynxeye.de>
> >
> > Seems your git send-email ignored this.
> 
> Did it? I checked the original mail's header and it says:
> 
> From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> Cc: barebox@lists.infradead.org, Lucas Stach <dev@lynxeye.de>
> Subject: [PATCH v2] USB: xHCI: Sync non-coherent DMA buffers
> 
> I also checked http://www.spinics.net/lists/u-boot-v2/msg23105.html
> which does not show Lucas on Cc.
> 
> @Lucas, did you receive the original mail or should I worry about
> my git-email setup?
> 
No worries. Your E-Mail setup is just fine. The barebox mailinglist
seems to eat the CC list, which is a bit annoying.

Regards,
Lucas
-- 
Pengutronix e.K.             | Lucas Stach                 |
Industrial Linux Solutions   | http://www.pengutronix.de/  |


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-04-15  9:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10  1:01 [PATCH 0/4] Some fixes for PCI, mvneta, xHCI Sebastian Hesselbarth
2015-04-10  1:01 ` [PATCH 1/4] pci: fix device registration for directly attached devices Sebastian Hesselbarth
2015-04-10  7:15   ` Lucas Stach
2015-04-10  8:24     ` Sebastian Hesselbarth
2015-04-10  1:01 ` [PATCH 2/4] net: mvneta: Fix transmit errors due to dirty txdesc Sebastian Hesselbarth
2015-04-13  6:43   ` Sascha Hauer
2015-04-10  1:01 ` [PATCH 3/4] net: mvneta: Remove unnecessary DMA ops Sebastian Hesselbarth
2015-04-10  7:23   ` Lucas Stach
2015-04-10  8:18     ` Sebastian Hesselbarth
2015-04-10 16:09       ` Jan Lübbe
2015-04-10  1:01 ` [PATCH 4/4] USB: xHCI: Sync non-coherent DMA buffers Sebastian Hesselbarth
2015-04-10  7:25   ` Lucas Stach
2015-04-13 14:22   ` [PATCH v2] " Sebastian Hesselbarth
2015-04-14 18:52     ` Sascha Hauer
2015-04-14 19:29       ` Sebastian Hesselbarth
2015-04-15  9:11         ` Lucas Stach [this message]
2015-04-15  9:10     ` Lucas Stach
2015-04-15 12:06     ` Sascha Hauer

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=1429089107.3365.11.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sebastian.hesselbarth@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox