From: Paul Mundt <lethal@linux-sh.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Peter H?we <PeterHuewe@gmx.de>, Magnus Damm <damm@igel.co.jp>,
linux-kernel@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH] serial/sh_sci: Fix build failure for non-sh architectures
Date: Wed, 10 Mar 2010 17:08:41 +0900 [thread overview]
Message-ID: <20100310080841.GF19518@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1003100854320.4618@axis700.grange>
On Wed, Mar 10, 2010 at 09:00:24AM +0100, Guennadi Liakhovetski wrote:
> On Wed, 10 Mar 2010, Paul Mundt wrote:
>
> > On Tue, Mar 09, 2010 at 09:18:25PM +0100, Peter H?we wrote:
> > > From: Peter Huewe <peterhuewe@gmx.de>
> > >
> > > This patch fixes a build failure for various arm based defconfigs
> > > [1][2][3] and maybe other architectures/configs.
> > >
> > > The build failure was introduced by the sh specific patch [4]
> > > "serial: sh-sci: Add DMA support"
> > > by Guennadi Liakhovetski
> > >
> > > Patch against linux-next of 20100309
> >
> > Please Cc linux-sh@vger.kernel.org so these things make it in to
> > patchwork in the future.
>
> Ok, I understand, this breakage is only in linux-next, and only for
> shmobile targets, which wasn't there as I was preparing the patch.
> However, what I did oversee is the H8300 arch, which also uses the
> sh-sci.c, and they are, probably, also broken in the mainline now. So, can
> we, please, also schedule this for 34-rc2?
>
Yes, it's in my .34 queue. H8300 doesn't actually matter though, since
they've never converted in-tree to using sh-sci through the driver model.
It likely hasn't been tested on H8 since 2.5, so I'm not exactly losing
sleep over it.
prev parent reply other threads:[~2010-03-10 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 20:18 [PATCH] serial/sh_sci: Fix build failure for non-sh architectures Peter Hüwe
2010-03-10 2:53 ` Paul Mundt
2010-03-10 8:00 ` Guennadi Liakhovetski
2010-03-10 8:08 ` 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=20100310080841.GF19518@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=PeterHuewe@gmx.de \
--cc=damm@igel.co.jp \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.