public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c-next pull request
Date: Tue, 6 Jan 2009 16:21:45 +0000	[thread overview]
Message-ID: <20090106162145.GJ8032@fluff.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0901051858250.3057-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Mon, Jan 05, 2009 at 07:01:34PM -0800, Linus Torvalds wrote:
> 
> 
> On Mon, 5 Jan 2009, Ben Dooks wrote:
> >
> > are available in the git repository at:
> > 
> >   git://aeryn.fluff.org.uk/bjdooks/linux.git i2c-next
> 
> I fixed up a conflict that _looked_ trivial in 
> drivers/i2c/busses/i2c-s3c2410.c, and since I can't even compile-test it, 
> you should double-check. We had one branch remove the need for 
> regs-gpio.h, and the ARM merge had moved the header files around..
> 
> All the commits in question were actually yours, they just came in from 
> different trees. So if it's not right, I'm sure you can fix it up ;)

Thanks, it compiles fine on the s3c6400, will test the s3c24xx build
later.

-- 
Ben (ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

      parent reply	other threads:[~2009-01-06 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 10:57 i2c-next pull request Ben Dooks
     [not found] ` <E1LJn9P-00013j-2W-fIsYBodh/r28n8r38hOLvmD2FQJk+8+b@public.gmane.org>
2009-01-06  3:01   ` Linus Torvalds
     [not found]     ` <alpine.LFD.2.00.0901051858250.3057-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-01-06 16:21       ` Ben Dooks [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=20090106162145.GJ8032@fluff.org.uk \
    --to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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