From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] video: msm: Fix section mismatches in mddi.c
Date: Mon, 23 Apr 2012 09:19:41 -0700 [thread overview]
Message-ID: <20120423161941.GA26903@codeaurora.org> (raw)
In-Reply-To: <4F94F3D7.5030904@gmx.de>
On Mon, Apr 23, 2012 at 06:16:55AM +0000, Florian Tobias Schandinat wrote:
> On 04/12/2012 06:45 PM, David Brown wrote:
> > The change
> > commit 461cbe77d0a4f887c33a3a95ea68a7daf23b4302
> > Author: Gregory Bean <gbean@codeaurora.org>
> > Date: Wed Jul 28 10:22:13 2010 -0700
> >
> > video: msm: Fix section mismatch in mddi.c.
> >
> > fixes a section mismatch between the board file and the driver's probe
> > function, however, it misses the additional mismatches between the
> > probe function and some routines it calls. Fix these up as well.
> >
> > Signed-off-by: David Brown <davidb@codeaurora.org>
>
> Applied.
Hmm. I guess it is somewhat my fault, since I sent the message To
both myself and you. I've already applied this to the MSM tree, and I
believe it has been merged into Linus' tree. I don't think it'll be
an issue, since git merge will handle the duplicate patch fine.
Next time, I'll try to be clearer about which tree I'm thinking for a
patch to go through.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2012-04-23 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 18:45 [PATCH 1/2] video: msm: Fix section mismatches in mddi.c David Brown
2012-04-12 18:45 ` [PATCH 2/2] ARM: msm: Fix section mismatches in proc_comm.c David Brown
2012-04-23 6:16 ` [PATCH 1/2] video: msm: Fix section mismatches in mddi.c Florian Tobias Schandinat
2012-04-23 16:19 ` David Brown [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=20120423161941.GA26903@codeaurora.org \
--to=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).