All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Rob Herring <robh@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	SH-Linux <linux-sh@vger.kernel.org>,
	Linux USB List <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2] extcon: add Maxim MAX3355 driver
Date: Mon, 14 Dec 2015 23:44:46 +0000	[thread overview]
Message-ID: <20151214234446.GA10671@kroah.com> (raw)
In-Reply-To: <566F42BF.30109@cogentembedded.com>

On Tue, Dec 15, 2015 at 01:29:19AM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 12/15/2015 01:21 AM, Rob Herring wrote:
> 
> >>>>Maxim  Integrated MAX3355E chip integrates a  charge pump and comparators
> >>>>to
> >>>>enable a system with an integrated USB OTG dual-role transceiver to
> >>>>function
> >>>>as  an USB  OTG dual-role device.  In addition  to sensing/controlling
> >>>>Vbus,
> >>>>the chip also passes thru the ID signal  from the USB  OTG connector.
> >>>>On some Renesas boards,  this signal is  just fed into the SoC thru a
> >>>>GPIO
> >>>>pin --  there's no real  OTG controller, only host and gadget USB
> >>>>controllers
> >>>>sharing the same USB bus; however, we'd  like to allow host or gadget
> >>>>drivers
> >>>>to be loaded depending on the cable type,  hence the need for the MAX3355
> >>>>extcon driver. The Vbus status signals are also  wired to GPIOs (however,
> >>>>we
> >>>>aren't currently interested in them),  the OFFVBUS# signal is controlled
> >>>>by
> >>>>the host controllers, there's  also the SHDN# signal wired to a GPIO, it
> >>>>should be driven high for the  normal operation.
> >>>
> >>>
> >>>As multiple people have said, fix the spacing here.
> >>
> >>
> >>    You are the first to complain abou _this_ patch. If you don't have other
> >>issues with this driver in which case you should have trimmed the reply at
> >>this point), I'd like to keep my spacing as is. Thank you.
> >
> >Your previous version was not "extcon-usb-gpio: add enable pin
> >support"[1] which has now been re-written to be max3355 specific?
> 
>    No, the MAX3355 driver pre-dates that version. First there was a driver,
> then I tried to re-use the existing stuff (there was no extcon-usb-gpio at
> the time of writing my driver), then had to return to the separate driver
> idea...
> 
> >"So
> >what" and "I'd like to keep my spacing as is" aren't valid reasons.
> >Fix it, then I'll look at the rest again.
> 
>    I'll consider doing that if you care to explain what's the problem with
> my spacing. TIA.

You are mixing 2 and 1 spaces between words, don't do that.

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Rob Herring <robh@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	SH-Linux <linux-sh@vger.kernel.org>,
	Linux USB List <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v2] extcon: add Maxim MAX3355 driver
Date: Mon, 14 Dec 2015 15:44:46 -0800	[thread overview]
Message-ID: <20151214234446.GA10671@kroah.com> (raw)
In-Reply-To: <566F42BF.30109@cogentembedded.com>

On Tue, Dec 15, 2015 at 01:29:19AM +0300, Sergei Shtylyov wrote:
> Hello.
> 
> On 12/15/2015 01:21 AM, Rob Herring wrote:
> 
> >>>>Maxim  Integrated MAX3355E chip integrates a  charge pump and comparators
> >>>>to
> >>>>enable a system with an integrated USB OTG dual-role transceiver to
> >>>>function
> >>>>as  an USB  OTG dual-role device.  In addition  to sensing/controlling
> >>>>Vbus,
> >>>>the chip also passes thru the ID signal  from the USB  OTG connector.
> >>>>On some Renesas boards,  this signal is  just fed into the SoC thru a
> >>>>GPIO
> >>>>pin --  there's no real  OTG controller, only host and gadget USB
> >>>>controllers
> >>>>sharing the same USB bus; however, we'd  like to allow host or gadget
> >>>>drivers
> >>>>to be loaded depending on the cable type,  hence the need for the MAX3355
> >>>>extcon driver. The Vbus status signals are also  wired to GPIOs (however,
> >>>>we
> >>>>aren't currently interested in them),  the OFFVBUS# signal is controlled
> >>>>by
> >>>>the host controllers, there's  also the SHDN# signal wired to a GPIO, it
> >>>>should be driven high for the  normal operation.
> >>>
> >>>
> >>>As multiple people have said, fix the spacing here.
> >>
> >>
> >>    You are the first to complain abou _this_ patch. If you don't have other
> >>issues with this driver in which case you should have trimmed the reply at
> >>this point), I'd like to keep my spacing as is. Thank you.
> >
> >Your previous version was not "extcon-usb-gpio: add enable pin
> >support"[1] which has now been re-written to be max3355 specific?
> 
>    No, the MAX3355 driver pre-dates that version. First there was a driver,
> then I tried to re-use the existing stuff (there was no extcon-usb-gpio at
> the time of writing my driver), then had to return to the separate driver
> idea...
> 
> >"So
> >what" and "I'd like to keep my spacing as is" aren't valid reasons.
> >Fix it, then I'll look at the rest again.
> 
>    I'll consider doing that if you care to explain what's the problem with
> my spacing. TIA.

You are mixing 2 and 1 spaces between words, don't do that.

  reply	other threads:[~2015-12-14 23:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 23:22 [PATCH v2] extcon: add Maxim MAX3355 driver Sergei Shtylyov
2015-12-11 23:22 ` Sergei Shtylyov
2015-12-11 23:22 ` Sergei Shtylyov
2015-12-14  1:24 ` Rob Herring
2015-12-14  1:24   ` Rob Herring
2015-12-14 17:36   ` Sergei Shtylyov
2015-12-14 17:36     ` Sergei Shtylyov
     [not found]     ` <566EFE0A.4000104-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-14 22:21       ` Rob Herring
2015-12-14 22:21         ` Rob Herring
2015-12-14 22:21         ` Rob Herring
2015-12-14 22:29         ` Sergei Shtylyov
2015-12-14 22:29           ` Sergei Shtylyov
2015-12-14 23:44           ` Greg KH [this message]
2015-12-14 23:44             ` Greg KH
2015-12-15 11:24             ` Sergei Shtylyov
2015-12-15 11:24               ` Sergei Shtylyov
     [not found]               ` <566FF888.8060200-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-15 11:28                 ` Geert Uytterhoeven
2015-12-15 11:28                   ` Geert Uytterhoeven
2015-12-15 11:28                   ` Geert Uytterhoeven
2015-12-15 11:54                   ` Sergei Shtylyov
2015-12-15 11:54                     ` Sergei Shtylyov
2015-12-15 12:12                     ` Geert Uytterhoeven
2015-12-15 12:12                       ` Geert Uytterhoeven
2015-12-15 18:51               ` Greg KH
2015-12-15 18:51                 ` Greg KH
     [not found]                 ` <20151215185156.GD16129-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-12-15 19:09                   ` Sergei Shtylyov
2015-12-15 19:09                     ` Sergei Shtylyov
2015-12-15 19:09                     ` Sergei Shtylyov
2015-12-15  1:20 ` Chanwoo Choi
2015-12-15  1:20   ` Chanwoo Choi
2015-12-15 19:11   ` Sergei Shtylyov
2015-12-15 19:11     ` Sergei Shtylyov

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=20151214234446.GA10671@kroah.com \
    --to=greg@kroah.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=pawel.moll@arm.com \
    --cc=robh@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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 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.