public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: "Jeremy C. Andrus"
	<jeremya-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>,
	Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
	Laxman Dewangan
	<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
Subject: Re: [RFC PATCH 0/5] Minor bugfixes for Tegra kernels
Date: Wed, 16 Jan 2013 14:45:00 -0700	[thread overview]
Message-ID: <50F71F5C.6020209@wwwdotorg.org> (raw)
In-Reply-To: <1358366173-56861-1-git-send-email-jeremya-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>

On 01/16/2013 12:56 PM, Jeremy C. Andrus wrote:
> From: "Jeremy C. Andrus" <jeremya-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
> 
> In the course of my research here at Columbia University, I have been
> doing some kernel development on the Google Nexus 7 device. I took the
> time to address most of the compile-time warnings while building the
> Tegra kernel tree using the cross-compiler shipped with Android
> (gcc-4.7), and in doing so I came across a few minor issues.
> 
> This RFC series addresses several minor bugs that I was able to fix
> while suppressing compile warnings. Not knowing exactly where
> to send the patches, I decided to send them primarily to the Tegra
> list serv in hopes that they will find their way to the correct place.
> 
> All 5 patches apply cleanly the kernel/tegra repository hosted by
> Google. I used the commit hash referenced in the Android device tree
> git logs as my HEAD revision: 22b4fcde206e96f57bf0a111403fc3d75532918a
> I belive that this is the revision which corresponds to the prebuilt
> kernel provided in the Jelly Bean release.

I honestly don't know where you should send these patches. I've CC'd
Colin Cross who works on Android in case he can clue us in. I assume
there's a Gerrit instance somewhere for Android that you need to push
these into...

Laxman, can you please check if any of these patches should be applied
to our internal/downstream kernels?

Jeremy, do patches 3 or 4 need to be applied to the mainline kernel? It
may be useful for you to resend those directly to the relevant upstream
subsystem maintainers, after rebasing them onto the latest upstream
code. See Documentation/SubmittingPatches in the mainline kernel.

Thanks for the contributions!

  parent reply	other threads:[~2013-01-16 21:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 19:56 [RFC PATCH 0/5] Minor bugfixes for Tegra kernels Jeremy C. Andrus
     [not found] ` <1358366173-56861-1-git-send-email-jeremya-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2013-01-16 19:56   ` [RFC PATCH 1/5] arm: tegra: Fix build under Android cross-compiler Jeremy C. Andrus
2013-01-16 19:56   ` [RFC PATCH 2/5] arm: tegra: Fix modem_reset_flag assignment Jeremy C. Andrus
2013-01-16 19:56   ` [RFC PATCH 3/5] power: smb347: Fix stack corruption Jeremy C. Andrus
2013-01-16 19:56   ` [RFC PATCH 4/5] input: lid: Fix init function ignores sysfs retval Jeremy C. Andrus
2013-01-16 19:56   ` [RFC PATCH 5/5] input: touchscreen: Fix rmi4 sysfs and driver removal Jeremy C. Andrus
2013-01-16 21:45   ` Stephen Warren [this message]
     [not found]     ` <50F71F5C.6020209-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-17  2:07       ` [RFC PATCH 0/5] Minor bugfixes for Tegra kernels Jeremy Andrus
     [not found]         ` <1024EDB1-9A14-4308-8245-7EFB98ADBD0E-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2013-01-17  2:37           ` Colin Cross
     [not found]             ` <CAMbhsRTc4m-4pRF9+w=6ekueQiwaa8N1vOaX2vggd0Pi_MqAFQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-17  5:35               ` Jeremy Andrus

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=50F71F5C.6020209@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=jeremya-eQaUEPhvms7ENvBUuze7eA@public.gmane.org \
    --cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@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