From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: John Linn <John.Linn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2c of mux patches inquiry
Date: Tue, 24 Apr 2012 18:08:57 +0200 [thread overview]
Message-ID: <20120424160857.GB9007@pengutronix.de> (raw)
In-Reply-To: <e3d3b989-3996-49c7-86fc-2d04873e9e72-dAX9Bq04yCSXHCJdrdq+zrjjLBE8jN/0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Tue, Apr 24, 2012 at 09:33:08AM -0600, John Linn wrote:
> Hi guys,
>
> What's the odds of the i2c/of: mux patches making into upstream?
>
> It looks like they're getting some momentum, nice work!
Thanks!
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h
> =2d9b178f1d5ff652850410b36842b4401ab7e319
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h
> =7e865fe1ffa449d7f4f5a1946aa0f28b05afcbee
>
> I really want to start using them but also don't like to get a
> dependency on stuff that never makes it upstream.
They are scheduled for the 3.5 merge window. I don't put stuff into my
next branch which I don't intend to send upstream (short-term or
mid-term).
You do have an influence regarding upstreaming by donating tags like
Acked-by, Tested-by or Reviewed-by.
And please ask such questions on the lists, not personally.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
parent reply other threads:[~2012-04-24 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e3d3b989-3996-49c7-86fc-2d04873e9e72-dAX9Bq04yCSXHCJdrdq+zrjjLBE8jN/0@public.gmane.org>]
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=20120424160857.GB9007@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=John.Linn-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@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;
as well as URLs for NNTP newsgroup(s).