public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Axel Haslam <ahaslam@baylibre.com>
Cc: Kevin Hilman <khilman@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
	David Lechner <david@lechnology.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	kishon@ti.com
Subject: Re: [PATCH v2 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx
Date: Wed, 23 Nov 2016 10:32:20 +0100	[thread overview]
Message-ID: <20161123093220.GA32502@kroah.com> (raw)
In-Reply-To: <CAKXjFTME9Y+KEg21i05zP6+10tB4bW=cMbSftAbYhozEg1B8ZA@mail.gmail.com>

On Mon, Nov 21, 2016 at 06:10:50PM +0100, Axel Haslam wrote:
> Hi Greg,
> 
> On Thu, Nov 3, 2016 at 5:03 PM, Axel Haslam <ahaslam@baylibre.com> wrote:
> > The davinci ohci driver name (currently "ohci") is too generic.
> > To be consistent with other usb dirvers, append the "-da8xx" postfix
> > to the name.
> >
> 
> if there are no objections, would it be possible to pick up this patch?
> the corresponding phy patch was merged and the platform changes
> are ack'ed, and will we taken by the davinci maintainer once this patch
> gets in.

Now applied.

thanks,

greg k-h

  reply	other threads:[~2016-11-23  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 16:03 [PATCH v2 0/3] davinci: ohci: fix usb ohci device name Axel Haslam
2016-11-03 16:03 ` [PATCH v2 1/3] ARM: davinci: da8xx: Fix " Axel Haslam
2016-11-23 12:07   ` Sekhar Nori
2016-11-03 16:03 ` [PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx Axel Haslam
2016-11-05  5:21   ` Kishon Vijay Abraham I
2016-11-03 16:03 ` [PATCH v2 3/3] usb: ohci-da8xx: rename driver " Axel Haslam
2016-11-21 17:10   ` Axel Haslam
2016-11-23  9:32     ` Greg KH [this message]
2016-11-03 16:49 ` [PATCH v2 0/3] davinci: ohci: fix usb ohci device name David Lechner

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=20161123093220.GA32502@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ahaslam@baylibre.com \
    --cc=david@lechnology.com \
    --cc=khilman@kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nsekhar@ti.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