From: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Any more i2c driver fixes or new drivers to check?
Date: Tue, 16 Dec 2008 22:11:58 +0000 [thread overview]
Message-ID: <20081216221158.GG8032@fluff.org.uk> (raw)
In-Reply-To: <20081216210907.GA2601-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On Tue, Dec 16, 2008 at 01:09:09PM -0800, Tony Lindgren wrote:
> * Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org> [081216 13:58]:
> > Are there any more fixes that anyone would like considering
> > for the current kernel, or new drivers to look at before the
> > next merge window.
> >
> > Any drivers or updates not on this list by 2008-12-19 will be too late
> > for the next merge.
>
> Well there's the i2c-omap.c series for the next merge window,
> but I guess that's already on your merge list?
done.
> Maybe post a list of what your're planning to merge so people will
> know if it's going in or not. Or do you have a link to your git-branch
> of the stuff going upstream?
Already done, my dev machine now has a replacement CPU and memory and
seems to be stable now.
--
Ben (ben-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2008-12-16 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 21:56 Any more i2c driver fixes or new drivers to check? Ben Dooks
[not found] ` <20081216215628.GD8032-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-12-16 21:09 ` Tony Lindgren
[not found] ` <20081216210907.GA2601-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2008-12-16 22:11 ` Ben Dooks [this message]
[not found] ` <20081216221158.GG8032-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2008-12-16 21:20 ` Tony Lindgren
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=20081216221158.GG8032@fluff.org.uk \
--to=ben-linux-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.