From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ARM kernel mailing list
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: Stable I2C branch needed as a dependency for Tegra change
Date: Sat, 12 May 2012 22:21:59 -0600 [thread overview]
Message-ID: <4FAF36E7.1070104@wwwdotorg.org> (raw)
In-Reply-To: <20120512184515.GC28973-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On 05/12/2012 12:45 PM, Wolfram Sang wrote:
> Hi,
>
>> Is your i2c-embedded/for-next branch stable (i.e. that commit
>> will not be rebased between now and when you send a pull request
>> for 3.5), so I can use it as a baseline for a Tegra branch? If
>> not, could you let me know when it is stable, so I can create the
>> Tegra branch as that time.
>
> Because of my holidays coming along, I'd think my for-next branch
> is done now (except for additions maybe). Yet, when and how to
> rewind the branch and/or offering a stable base in general is
> another thing I need to scratch my head about afterwards.
No worries then; I'll hold the dependent patch until 3.6; that way
there won't be any specific dependencies.
prev parent reply other threads:[~2012-05-13 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 23:19 Stable I2C branch needed as a dependency for Tegra change Stephen Warren
[not found] ` <4FA31297.8000904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-05-12 18:45 ` Wolfram Sang
[not found] ` <20120512184515.GC28973-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-05-13 4:21 ` Stephen Warren [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=4FAF36E7.1070104@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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).