linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: rcar-dmac: Update copyright information
Date: Tue, 4 Jun 2019 11:38:27 +0200	[thread overview]
Message-ID: <20190604093826.tawdq7hz22pxjn36@verge.net.au> (raw)
In-Reply-To: <OSAPR01MB3089A2D7AB64489BB58CF5FED8150@OSAPR01MB3089.jpnprd01.prod.outlook.com>

On Tue, Jun 04, 2019 at 04:20:52AM +0000, Yoshihiro Shimoda wrote:
> Hi Simon-san again,
> (clean up on CC)
> 
> This is just a record.
> 
> > From: Simon Horman, Sent: Monday, May 13, 2019 9:20 PM
> <snip>
> > > > Shimoda-san, can we go further and also:
> > > >
> > > > 1. Remove the r8a66597-udc driver, which also seems unused
> 
> I overlooked that some SuperH platforms used this driver like below.
> So, I will not submit removing this driver patch at this time.
> 
> $ git grep -l r8a66597_udc
> arch/sh/boards/mach-ecovec24/setup.c
> arch/sh/boards/mach-kfr2r09/setup.c
> arch/sh/boards/mach-se/7724/setup.c

Thanks for looking into this.
I agree we should keep the r8a66597-udc driver for now.

> > > > 2. Remove (minimal) sudmac integration from usbhs ?
> 
> I have submitted a patch like below:
> https://patchwork.kernel.org/patch/10974161/

Thanks!

  reply	other threads:[~2019-06-04  9:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 18:26 [PATCH] dmaengine: rcar-dmac: Update copyright information Niklas Söderlund
2019-04-11  8:49 ` Simon Horman
2019-04-11 15:17   ` Niklas Söderlund
2019-04-24 12:22     ` Geert Uytterhoeven
2019-04-25  3:52       ` Yoshihiro Shimoda
2019-04-26 11:53         ` Vinod Koul
2019-05-09 12:55           ` Simon Horman
2019-05-10 11:03             ` Yoshihiro Shimoda
2019-05-13 12:20               ` Simon Horman
2019-06-04  4:20                 ` Yoshihiro Shimoda
2019-06-04  9:38                   ` Simon Horman [this message]
2019-04-26 11:54 ` Vinod Koul

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=20190604093826.tawdq7hz22pxjn36@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=yoshihiro.shimoda.uh@renesas.com \
    /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).