All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Geis <pgwipeout@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] Add sw2_sw4 voltage table to cpcap regulator.
Date: Mon, 23 Jul 2018 13:57:44 -0400	[thread overview]
Message-ID: <63de1504-5fc7-ee9c-9d91-69d0b2e3b944@gmail.com> (raw)
In-Reply-To: <20180723170157.GD13981@sirena.org.uk>

On 07/23/2018 01:01 PM, Mark Brown wrote:
> On Fri, Jul 20, 2018 at 08:43:49PM -0400, Peter Geis wrote:
>> SW2 and SW4 use a shared table to provide voltage to the cpu core and
>> devices on Tegra hardware.
>> Added this table to the cpcap regulator driver as the first step to
>> supporting this device on Tegra.
> 
> This fails to apply with:
> 
> Applying: Add sw2_sw4 voltage table to cpcap regulator.
> .git/rebase-apply/patch:37: trailing whitespace.
>                                                 1437500, 1450000,
> error: corrupt patch at line 38
> Patch failed at 0001 Add sw2_sw4 voltage table to cpcap regulator.
> 
> Please check and resend.
> 
Apologies, I accidentally converted all of the tabs to spaces.
Re-sending both patches with tabulation intact.

  reply	other threads:[~2018-07-23 17:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21  0:43 [PATCH 1/2] Add sw2_sw4 voltage table to cpcap regulator Peter Geis
2018-07-23 17:01 ` Mark Brown
2018-07-23 17:57   ` Peter Geis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-21 11:23 Peter Geis
2018-07-23 10:25 ` Mark Brown
2018-07-23 17:58 Peter Geis
2018-07-23 18:13 ` Mark Brown
2018-07-23 18:37   ` Peter Geis
2018-07-23 19:20     ` Dmitry Osipenko
2018-07-23 19:43       ` Peter Geis

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=63de1504-5fc7-ee9c-9d91-69d0b2e3b944@gmail.com \
    --to=pgwipeout@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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 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.