All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>
Cc: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Wolfram Sang <wsa@the-dreams.de>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH v4 4/4] arm64: dts: r8a7796: salvator-x: add SCIF1 (DEBUG1)
Date: Mon, 13 Feb 2017 14:10:25 +0100	[thread overview]
Message-ID: <CAMuHMdUpXaZ1Piiig7g0xiAd=mC18AN2zT095GB8t-NURyzSUw@mail.gmail.com> (raw)
In-Reply-To: <20170213130531.GE29718@verge.net.au>

Hi Simon,

On Mon, Feb 13, 2017 at 2:05 PM, Simon Horman <horms@verge.net.au> wrote:
> On Wed, Feb 08, 2017 at 12:19:55PM +0100, Ulrich Hecht wrote:
>> On Wed, Feb 8, 2017 at 11:54 AM, Simon Horman <horms@verge.net.au> wrote:
>> > On Fri, Feb 03, 2017 at 11:38:20AM +0100, Ulrich Hecht wrote:
>> >> Enables the SCIF hooked up to the DEBUG1 connector.
>> >>
>> >> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
>> >> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> >
>> > Hi Ulrich,
>> >
>> > could you clarify the dependency of this patch on earlier ones in the
>> > series. Is it safe to queue this up independently of the other patches?
>>
>> It does not actually depend on the other patches. I think I included
>> it here because I used that port for testing. Should be safe.
>
> Thanks but I dont' seem to have scif1 in r8a7796.dtsi.
> Should this patch be updated to use hscif1 which is (now) present in
> r8a7796.dtsi?

Nah, you just need

[PATCH v2 2/3] arm64: renesas: r8a7796: Add all SCIF nodes

first :-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2017-02-13 13:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 10:38 [PATCH v4 0/4] Renesas *SCIF* RX FIFO support Ulrich Hecht
2017-02-03 10:38 ` [PATCH v4 1/4] serial: sh-sci: increase RX FIFO trigger defaults for (H)SCIF Ulrich Hecht
2017-02-07 14:40   ` Geert Uytterhoeven
2017-02-03 10:38 ` [PATCH v4 2/4] serial: sh-sci: SCIFA/B RX FIFO software timeout Ulrich Hecht
2017-02-03 10:38 ` [PATCH v4 3/4] serial: sh-sci: make RX FIFO parameters tunable via sysfs Ulrich Hecht
2017-02-07 14:40   ` Geert Uytterhoeven
2017-02-08 10:04     ` Ulrich Hecht
2017-02-08 10:38       ` Geert Uytterhoeven
2017-02-12 16:04   ` Laurent Pinchart
2017-02-03 10:38 ` [PATCH v4 4/4] arm64: dts: r8a7796: salvator-x: add SCIF1 (DEBUG1) Ulrich Hecht
2017-02-08 10:54   ` Simon Horman
2017-02-08 11:19     ` Ulrich Hecht
2017-02-13 13:05       ` Simon Horman
2017-02-13 13:10         ` Geert Uytterhoeven [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='CAMuHMdUpXaZ1Piiig7g0xiAd=mC18AN2zT095GB8t-NURyzSUw@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=ulrich.hecht+renesas@gmail.com \
    --cc=wsa@the-dreams.de \
    /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.