From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/02] ARM: shmobile: r8a7793 GOSE board HDMI prototype
Date: Wed, 25 Nov 2015 00:13:20 +0000 [thread overview]
Message-ID: <20151125001320.GC20596@verge.net.au> (raw)
In-Reply-To: <20151116091515.20711.14784.sendpatchset@little-apple>
On Tue, Nov 24, 2015 at 12:05:30PM +0900, Magnus Damm wrote:
> Hi Simon,
>
> On Tue, Nov 24, 2015 at 11:53 AM, Simon Horman <horms@verge.net.au> wrote:
> > Hi Magnus,
> >
> > On Mon, Nov 16, 2015 at 06:15:15PM +0900, Magnus Damm wrote:
> >> ARM: shmobile: r8a7793 GOSE board HDMI prototype
> >>
> >> [PATCH 01/02] ARM: shmobile: r8a7793: Add DU node to device tree
> >> [PATCH 02/02] ARM: shmobile: r8a7793: gose: HDMI prototype hack
> >>
> >> These patches include HDMI prototype support for the r8a7793 GOSE board.
> >> No special merge time dependencies exist, however for correct run time
> >> operation v4.4-rc1 is recommended and in particular the patch
> >> "drm: rcar-du: Add support for the R8A7793 DU".
> >>
> >> Tested with the modetest utility on the r8a7793 GOSE board.
> >> # modetest -M rcar-du -c
> >> # modetest -M rcar-du -s 33:1280x720@AR24
> >>
> >> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> >
> > It would help me somewhat if you could prefix prototype patches with
> > RFC or PATCH/RFC. Thanks.
>
> Yeah, I agree - sorry for constantly forgetting about the RFC portion.
>
> This particular series actually had the first patch as "ready to merge
> upstream" while the second one is a prototype that depends on I2C
> which I think is missing for r8a7793.
>
> Would it be possible for you to pick up the first patch and prioritise
> I2C over other devices on r8a7793? That way I can easily redo patch
> 2/2 and we get working HDMI upstream.
Sure, I'll look at queuing up patch 1/2.
However, a scheme where a series labeled prototype contains a patch ready
to merge and one not ready to merge is a little hard for me to follow.
I know its tedious but it would help in future if RFC and ready-to-merge
patches were in separate series and RFC were tags used. Thanks :)
prev parent reply other threads:[~2015-11-25 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 9:15 [PATCH 00/02] ARM: shmobile: r8a7793 GOSE board HDMI prototype Magnus Damm
2015-11-24 2:53 ` Simon Horman
2015-11-24 3:05 ` Magnus Damm
2015-11-25 0:13 ` Simon Horman [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=20151125001320.GC20596@verge.net.au \
--to=horms@verge.net.au \
--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