From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Lee Jones <lee.jones@linaro.org>, Felipe Balbi <balbi@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH v5 6/6] mfd: intel_vuport: Add Intel virtual USB port MFD Driver
Date: Fri, 18 Mar 2016 08:30:08 -0700 [thread overview]
Message-ID: <20160318153008.GC16489@kroah.com> (raw)
In-Reply-To: <56EBBFA9.30101@linux.intel.com>
On Fri, Mar 18, 2016 at 04:43:21PM +0800, Lu Baolu wrote:
>
>
> On 03/18/2016 04:09 PM, Lee Jones wrote:
> > On Fri, 18 Mar 2016, Lu Baolu wrote:
> >
> >> Some Intel platforms have an USB port mux controlled by GPIOs.
> >> There's a single ACPI platform device that provides both USB ID
> >> extcon device and a USB port mux device. This MFD driver will
> >> split the 2 devices for their respective drivers.
> >>
> >> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
> >> Suggested-by: David Cohen <david.a.cohen@linux.intel.com>
> > This should be at the top.
> >
> > You couldn't have written the patch before it was suggested.
>
> Yes. I will change this.
>
> >
> >> Reviewed-by: Felipe Balbi <balbi@kernel.org>
> >> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> > What is this sign-off meant to indicate?
>
> Fengguang's sign-off was added due to folding a patch contributed by
> his kbuild robot.
No, you can't do that, he only signed off on his fixup patch, not your
overall larger patch!
I'm going to stop you now and require you to get this properly reviewed,
and signed-off-by some experienced Intel kernel developers before I look
at this at all. Take advantage of the resources you have, don't force
the community to point out these basic mistakes.
Also, you know I'm not looking at new patches until after -rc1 is out,
so please wait until then before resending.
greg k-h
prev parent reply other threads:[~2016-03-18 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 6:32 [PATCH v5 0/6] usb: add support for Intel dual role port mux Lu Baolu
2016-03-18 6:32 ` [PATCH v5 1/6] extcon: usb-gpio: add device binding for platform device Lu Baolu
2016-03-18 6:32 ` [PATCH v5 2/6] extcon: usb-gpio: add support for ACPI gpio interface Lu Baolu
2016-03-18 6:32 ` [PATCH v5 3/6] usb: mux: add common code for Intel dual role port mux Lu Baolu
2016-03-18 7:52 ` Chanwoo Choi
2016-03-18 8:23 ` Lu Baolu
2016-03-18 6:32 ` [PATCH v5 4/6] usb: mux: add driver for Intel gpio controlled " Lu Baolu
2016-03-18 6:32 ` [PATCH v5 5/6] usb: mux: add driver for Intel drcfg " Lu Baolu
2016-03-18 6:32 ` [PATCH v5 6/6] mfd: intel_vuport: Add Intel virtual USB port MFD Driver Lu Baolu
2016-03-18 8:09 ` Lee Jones
2016-03-18 8:43 ` Lu Baolu
2016-03-18 15:30 ` Greg Kroah-Hartman [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=20160318153008.GC16489@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=cw00.choi@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=myungjoo.ham@samsung.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