From: Jonathan Cameron <jic23@kernel.org>
To: James Robinson <james_robinson@vuzix.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: Latest Git Repo
Date: Mon, 10 Dec 2012 22:04:04 +0000 [thread overview]
Message-ID: <50C65C54.6010100@kernel.org> (raw)
In-Reply-To: <loom.20121210T224225-931@post.gmane.org>
On 12/10/2012 09:46 PM, James Robinson wrote:
> I have looked around and I am unable to find the git rep. that everyone seems to
>
> be posting patches against. I looked at
>
> http://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-2.6.git/info/refs
>
> but I don't seem to see the [PATCH] [V5] Invensense MPU6050 Device Driver.
>
Indeed not. It's not been merged yet as it is still under review.
Personally I've not had time to spend on it since it was posted (a whole 3 days ago ;)
and would need a go ahead from Lars-Peter on this one seeing as he has been doing
much of the review work.
I believe it is very close to merging, but has unfortunately missed the 3.8 merge
cycle, so will not hit mainline now until 3.9. It will probably be a couple of weeks
before it hits the staging-next tree as Greg tends to only start pulling stuff
again once rc1 for a given cycle is out.
> changes.
>
> Am I pointing to the right place?
As long as you look at the staging-next branch of that tree then pretty much.
Stuff tends to get queued up in the togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
though often doesn't sit there for longer than it takes me to catch up with
my emails / Greg to decide to pull when he gets the request.
>
> Thanks for your time,
You are welcome.
Looking forward to your patches!
>
> James
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-12-10 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 21:46 Latest Git Repo James Robinson
2012-12-10 22:04 ` Jonathan Cameron [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=50C65C54.6010100@kernel.org \
--to=jic23@kernel.org \
--cc=james_robinson@vuzix.com \
--cc=linux-iio@vger.kernel.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).