linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] sh-pfc: r8a7779: Don't group USB OVC and PENC pins
Date: Fri, 31 May 2013 07:43:26 +0000	[thread overview]
Message-ID: <20130531074323.GA22356@verge.net.au> (raw)
In-Reply-To: <CAOesGMgrdyFi3GMz52CVnhzmOYHbR5=29Ua0iS8cNbSjg6r-2A@mail.gmail.com>

On Thu, May 30, 2013 at 11:11:36PM -0700, Olof Johansson wrote:
> On Thu, May 30, 2013 at 10:45 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, May 30, 2013 at 09:43:08PM -0700, Olof Johansson wrote:
> >> Hi,
> >>
> >> On Thu, May 30, 2013 at 5:17 PM, Simon Horman <horms@verge.net.au> wrote:
> >> > On Thu, May 30, 2013 at 10:08:56PM +0200, Linus Walleij wrote:
> >> >> On Thu, May 30, 2013 at 12:28 AM, Simon Horman
> >> >> <horms+renesas@verge.net.au> wrote:
> >> >>
> >> >> > From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> >> >> >
> >> >> > The USB_OVCn pins are alternate options for USB over-current detection
> >> >> > when using a 3.3V USB interface. As they're not mandatory they can be
> >> >> > used independently of the USB PENC pins. Don't group the USB_OVCn and
> >> >> > PENC pins to avoid conflicts when the USB_OVCn pins are used by another
> >> >> > function.
> >> >> >
> >> >> > Reported-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> >> >> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> >> >> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >> >>
> >> >> OK, Acked-by, do you want me to take this as a fix in the pinctrl
> >> >> tree for v3.10?
> >> >>
> >> >> Just asking because Simon usually takes everything else relating to
> >> >> the SH. ...
> >> >
> >> > This was a pull request from my tree to arm-soc, so thats they way
> >> > I was planning to handle things.
> >> >
> >> > Olof, Arnd,
> >> >
> >> > should I re-spin the pull request to include Linus's ack?
> >>
> >> You can if you want, but for an odd and specific fix like this we'll
> >> all know he's ok with the code going in.
> >
> > In that case my preference is to leave the pull request as is.
> > Could you consider merging it?
> 
> Yes, I will do a pass tomorrow and handle the outstanding merges.
> 
> > As an aside, I do expect to send some more v3.10 fixes for shmobile.
> > There seem to be more than usual.
> 
> A little unfortunate but it's hard to do much about.
> 
> Please be conservative with what you pick up for 3.10 vs 3.11 -- Linus
> has said he really wants to see things slow down.
> 
> And please make our case as easy as possible by making sure it's
> pretty clear from the patch descriptions what kind of bugs they fix
> (and if they are regressions).

Understood. I will be careful to only send the bare essentials for v3.10.

  parent reply	other threads:[~2013-05-31  7:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 22:28 [GIT PULL] Renesas ARM based SoC fixes for v3.10 Simon Horman
2013-05-29 22:28 ` [PATCH 1/2] sh-pfc: r8a7779: Don't group USB OVC and PENC pins Simon Horman
2013-05-29 22:35   ` Sergei Shtylyov
2013-05-29 23:51     ` Laurent Pinchart
2013-05-30 11:50       ` Sergei Shtylyov
2013-05-30 20:08   ` Linus Walleij
2013-05-31  0:17     ` Simon Horman
2013-05-31  4:43       ` Olof Johansson
2013-05-31  5:45         ` Simon Horman
2013-05-31  6:11           ` Olof Johansson
2013-05-31  7:21             ` Linus Walleij
2013-05-31 23:59               ` Simon Horman
2013-06-01  4:35               ` Olof Johansson
2013-05-31  7:43             ` Simon Horman [this message]
2013-05-29 22:28 ` [PATCH 2/2] ARM: shmobile: sh73a0: Update CMT clockevent rating to 80 Simon Horman
2013-06-01  4:41 ` [GIT PULL] Renesas ARM based SoC fixes for v3.10 Olof Johansson
2013-06-07  8:05   ` Simon Horman
  -- strict thread matches above, loose matches on Subject: below --
2013-06-04  7:46 [GIT PULL v3] " Simon Horman
2013-06-04  7:46 ` [PATCH 1/2] sh-pfc: r8a7779: Don't group USB OVC and PENC pins Simon Horman

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=20130531074323.GA22356@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).