public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kmcmarti-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: tegra on 3.11
Date: Tue, 20 Aug 2013 16:50:08 -0400	[thread overview]
Message-ID: <20130820205007.GL27560@redacted.bos.redhat.com> (raw)
In-Reply-To: <5213C0F2.9060909-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On Tue, Aug 20, 2013 at 01:18:10PM -0600, Stephen Warren wrote:
> On 08/20/2013 09:04 AM, Kyle McMartin wrote:
> > Hey guys,
> > 
> > Just a quick note, I needed to pull in the patch from
> > http://marc.info/?l=linux-tegra&m=137404750420372&w=2 in order to get
> > trimslice booting from its internal SATA when using dtb to boot.
> 
> Oh dear, I can reproduce this. It looks like I didn't notice this since
> I was probably testing linux-next with Mikko's patches applied on top in
> my local branch:-(
> 
> If that patch gets applied to v3.11, then it'll cause nasty merge
> conflicts with Mikko's other USB-related patches when v3.12 comes
> around. Plus, the patch is rather large for this late stage in the
> v3.11-rc series. I think the best way is to add regulator-always-on,
> regulator-boot-on properties to the relevant VBUS regulators. I'll try
> sending a patch for that...

Thanks, we've hit another issue in Fedora where that may or may not be
the kernel (life on the bleeding edge, sigh.) but I'll re-build a known
working kernel with your patch instead of the backport and let you know
if it works for us.

regards, Kyle

  parent reply	other threads:[~2013-08-20 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 15:04 tegra on 3.11 Kyle McMartin
     [not found] ` <20130820150418.GI27560-nxOev/eQj6CGu0OVIAPS5KfLeoKvNuZc@public.gmane.org>
2013-08-20 19:18   ` Stephen Warren
     [not found]     ` <5213C0F2.9060909-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-20 20:50       ` Kyle McMartin [this message]
     [not found]     ` <20130827213445.GI8764@redacted.bos.redhat.com>
     [not found]       ` <521D1D7F.7060006@wwwdotorg.org>
     [not found]         ` <521D1D7F.7060006-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-04 18:38           ` Kyle McMartin
     [not found]             ` <20130904183815.GC16338-nxOev/eQj6CGu0OVIAPS5KfLeoKvNuZc@public.gmane.org>
2013-09-05 21:14               ` Stephen Warren
     [not found]                 ` <5228F42F.50904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-05 21:43                   ` Kyle McMartin
2013-12-03 10:30               ` Thierry Reding
     [not found]                 ` <20131203103043.GI21178-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2013-12-03 16:44                   ` Kyle McMartin

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=20130820205007.GL27560@redacted.bos.redhat.com \
    --to=kmcmarti-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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