From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] soc-camera: fix compile breakage on SH
Date: Tue, 21 Oct 2008 03:45:52 +0000 [thread overview]
Message-ID: <20081021034552.GB29105@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0810142335400.10458@axis700.grange>
On Mon, Oct 20, 2008 at 07:44:09PM +0200, Guennadi Liakhovetski wrote:
> On Mon, 20 Oct 2008, Paul Mundt wrote:
>
> > > Last I checked - just before sending the previous email - it was not yet
> > > committed, but it is racy, you know:-)
> > >
> > Then I will merge the original in my tree and we can then focus on
> > getting the API changed properly, and making an incremental transition
> > that doesn't break all of the existing users in the process.
>
> Shall I ask Mauro to not merge the v4l part? It might still work...
>
Too late now, so I'll just merge the SH part separately. Please just try
to keep this in mind in the future so we do not have the same problem
again.
prev parent reply other threads:[~2008-10-21 3:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 18:39 sh/boards/mach-migor/setup.c build error Adrian Bunk
2008-10-14 21:53 ` [PATCH] soc-camera: fix compile breakage on SH Guennadi Liakhovetski
2008-10-15 3:33 ` Adrian Bunk
2008-10-15 5:20 ` Adrian Bunk
2008-10-15 6:28 ` Magnus Damm
2008-10-15 6:41 ` Guennadi Liakhovetski
2008-10-15 8:03 ` Magnus Damm
2008-10-15 8:26 ` Guennadi Liakhovetski
2008-10-15 8:55 ` Magnus Damm
2008-10-15 9:07 ` Guennadi Liakhovetski
2008-10-15 10:52 ` [PATCH v2] " Guennadi Liakhovetski
2008-10-16 23:08 ` Guennadi Liakhovetski
2008-10-16 23:16 ` [PATCH] " Guennadi Liakhovetski
2008-10-20 4:09 ` Paul Mundt
2008-10-20 7:02 ` Guennadi Liakhovetski
2008-10-20 12:45 ` Paul Mundt
2008-10-20 13:00 ` Guennadi Liakhovetski
2008-10-20 13:08 ` Paul Mundt
2008-10-20 17:44 ` Guennadi Liakhovetski
2008-10-21 3:45 ` Paul Mundt [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=20081021034552.GB29105@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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