linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram.de>
To: Ben Dooks <ben-linux@fluff.org>
Cc: Mike Ditto <mditto@consentry.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	linux-i2c@vger.kernel.org, khali@linux-fr.org,
	torvalds@linux-foundation.org
Subject: Re: Please pull bjdoo ks' i2c-fixes
Date: Thu, 18 Dec 2008 12:12:53 +0100	[thread overview]
Message-ID: <494A3035.30107@scram.de> (raw)
In-Reply-To: <20081218100635.GH8032@fluff.org.uk>

Ben Dooks schrieb:

> Ok, but this isn't really a fix, so I'll look at putting it into my
> i2c-next tree, not i2c-fixes.

That's OK for me.

Thanks,
Jochen

      reply	other threads:[~2008-12-18 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1LChEf-0000Ts-53@teyla.home.fluff.org>
2008-12-17 11:55 ` Please pull bjdoo ks' i2c-fixes Jochen Friedrich
2008-12-18 10:06   ` Ben Dooks
2008-12-18 11:12     ` Jochen Friedrich [this message]

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=494A3035.30107@scram.de \
    --to=jochen@scram.de \
    --cc=ben-linux@fluff.org \
    --cc=khali@linux-fr.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mditto@consentry.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;
as well as URLs for NNTP newsgroup(s).