From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: catalin.marinas@arm.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, mcgrof@gmail.com
Subject: Re: [PATCH v2 0/5] kmemleak: few small cleanups and clear command support
Date: Thu, 3 Sep 2009 09:01:32 +0300 [thread overview]
Message-ID: <84144f020909022301pab1b36buf10e24686438e8d8@mail.gmail.com> (raw)
In-Reply-To: <1251956140-5499-1-git-send-email-lrodriguez@atheros.com>
Hi Luis,
On Thu, Sep 3, 2009 at 8:35 AM, Luis R. Rodriguez<lrodriguez@atheros.com> wrote:
> Still not sure who this goes through so sending this to Linus.
Time zone difference alert! I'm sorry but I haven't yet figured out
how to answer my emails while I'm sleeping. :-)
Seriously though, the patches should go through Catalin's git tree
that's hiding somewhere.
Pekka
next prev parent reply other threads:[~2009-09-03 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 5:35 Luis R. Rodriguez
2009-09-03 5:35 ` [PATCH v2 1/5] kmemleak: use bool for true/false questions Luis R. Rodriguez
2009-09-03 5:35 ` [PATCH v2 2/5] kmemleak: add clear command support Luis R. Rodriguez
2009-09-03 16:52 ` Catalin Marinas
2009-09-04 20:26 ` Luis R. Rodriguez
2009-09-04 22:28 ` Catalin Marinas
2009-09-03 5:35 ` [PATCH v2 3/5] kmemleak: move common painting code together Luis R. Rodriguez
2009-09-03 5:35 ` [PATCH v2 4/5] kmemleak: fix sparse warning over overshadowed flags Luis R. Rodriguez
2009-09-03 16:55 ` Catalin Marinas
2009-09-03 18:05 ` Luis R. Rodriguez
2009-09-03 5:35 ` [PATCH v2 5/5] kmemleak: fix sparse warning for static declarations Luis R. Rodriguez
2009-09-03 6:01 ` Pekka Enberg [this message]
2009-09-03 8:30 ` [PATCH v2 0/5] kmemleak: few small cleanups and clear command support Catalin Marinas
2009-09-04 19:57 ` Luis R. Rodriguez
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=84144f020909022301pab1b36buf10e24686438e8d8@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mcgrof@gmail.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®