linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] regulator: ab8500: Decomission platform data header
Date: Sat, 5 Dec 2020 01:30:28 +0100	[thread overview]
Message-ID: <CACRpkda1AC2Mv6CdoB7O9vrvJVCR7dj6pAYNvSe9Z7+YhgK_cg@mail.gmail.com> (raw)
In-Reply-To: <20201204223008.GH4558@sirena.org.uk>

On Fri, Dec 4, 2020 at 11:30 PM Mark Brown <broonie@kernel.org> wrote:
> On Fri, Dec 04, 2020 at 03:03:42PM +0100, Linus Walleij wrote:
> > ---
> >  drivers/regulator/ab8500-ext.c   |  13 ++-
> >  drivers/regulator/ab8500.c       | 116 ++++++++++++++++++++++-
> >  include/linux/regulator/ab8500.h | 156 -------------------------------
> >  3 files changed, 127 insertions(+), 158 deletions(-)
> >  delete mode 100644 include/linux/regulator/ab8500.h
>
> There's also an include of the header in ab8500-core.c which isn't
> removed by either this or the previous patch and needs to be handled
> somehow.

Weird since I built it and booted it!
I wonder what I did wrong this time :(

OK I'll fix it up and test again. Build a clean
tree etc.

Thanks!
Linus Walleij

  reply	other threads:[~2020-12-05  0:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 14:03 [PATCH 1/2] regulator: ab8500: Remove unused platform data Linus Walleij
2020-12-04 14:03 ` [PATCH 2/2] regulator: ab8500: Decomission platform data header Linus Walleij
2020-12-04 22:30   ` Mark Brown
2020-12-05  0:30     ` Linus Walleij [this message]
2020-12-05  0:08   ` kernel test robot
2020-12-07  9:35 ` [PATCH 1/2] regulator: ab8500: Remove unused platform data Lee Jones
2021-01-13 15:28 ` Mark Brown

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=CACRpkda1AC2Mv6CdoB7O9vrvJVCR7dj6pAYNvSe9Z7+YhgK_cg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.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 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).