linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Venture <venture@google.com>
To: Olof Johansson <olof@lixom.net>
Cc: linux-aspeed@lists.ozlabs.org, Arnd Bergmann <arnd@arndb.de>,
	Andrew Jeffery <andrew@aj.id.au>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	soc@kernel.org, arm-soc <arm@kernel.org>,
	Joel Stanley <joel@jms.id.au>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] soc: add aspeed folder and misc drivers
Date: Mon, 29 Apr 2019 10:12:06 -0700	[thread overview]
Message-ID: <CAO=notwewAeeLz=LsOcSj=DakLGW0KjeDHALP5Nv2ckgkRqnFA@mail.gmail.com> (raw)
In-Reply-To: <20190429165137.mwj4ehhwerunbef4@localhost>

On Mon, Apr 29, 2019 at 10:08 AM Olof Johansson <olof@lixom.net> wrote:
>
> On Thu, Apr 25, 2019 at 07:25:49PM +0200, Greg KH wrote:
> > On Tue, Apr 23, 2019 at 08:28:14AM -0700, Patrick Venture wrote:
> > > On Tue, Apr 23, 2019 at 8:22 AM Patrick Venture <venture@google.com> wrote:
> > > >
> > > > On Tue, Apr 23, 2019 at 7:26 AM Patrick Venture <venture@google.com> wrote:
> > > > >
> > > > > Create a SoC folder for the ASPEED parts and place the misc drivers
> > > > > currently present into this folder.  These drivers are not generic part
> > > > > drivers, but rather only apply to the ASPEED SoCs.
> > > > >
> > > > > Signed-off-by: Patrick Venture <venture@google.com>
> > > >
> > > > Accidentally lost the Acked-by when re-sending this patchset as I
> > > > didn't see it on v1 before re-sending v2 to the larger audience.
> > >
> > > Since there was a change between v1 and v2, Arnd, I'd appreciate you
> > > Ack this version of the patchset since it changes when the soc/aspeed
> > > Makefile is followed.
> >
> > I have no objection for moving stuff out of drivers/misc/ so the SOC
> > maintainers are free to take this.
> >
> > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> I'm totally confused. This is the second "PATCH v2" of this patch that I came
> across, I already applied the first.

I think the issue here was that I added to the CC list another email
and so you may see the v2  without that mailing list, and a v2 with it
--

Does this require a v3?  I honestly didn't think so, but this was the
first time I had to add more people without needing other changes.

>
> Patrick: Follow up with incremental patch in case there's any difference.
> Meanwhile, please keep in mind that you're adding a lot of work for people when
> you respin patches without following up on the previous version. Thanks!

w.r.t this patch series.  I found an issue with v1, and released a v2
with the detail of what changed.  I thought that was the correct
approach.  I apologize for creating extra work, that's something
nobody needs.

>
>
> -Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-29 17:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 14:26 [PATCH v2] soc: add aspeed folder and misc drivers Patrick Venture
2019-04-23 15:22 ` Patrick Venture
2019-04-23 15:28   ` Patrick Venture
2019-04-25 17:25     ` Greg KH
2019-04-29  7:48       ` Joel Stanley
2019-04-29  8:07         ` Arnd Bergmann
2019-04-29 16:51       ` Olof Johansson
2019-04-29 17:12         ` Patrick Venture [this message]
2019-04-29 19:27           ` Olof Johansson
2019-04-29 19:35             ` Patrick Venture
2019-04-29 19:40               ` Patrick Venture
2019-04-29 17:12         ` Olof Johansson
2019-04-29 17:16           ` Patrick Venture
2019-04-29 17:19             ` Olof Johansson
2019-04-29 17:22               ` Patrick Venture
  -- strict thread matches above, loose matches on Subject: below --
2019-04-22 17:54 Patrick Venture
2019-04-22 19:24 ` Patrick Venture
2019-04-29 16:36   ` Olof Johansson

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='CAO=notwewAeeLz=LsOcSj=DakLGW0KjeDHALP5Nv2ckgkRqnFA@mail.gmail.com' \
    --to=venture@google.com \
    --cc=andrew@aj.id.au \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=soc@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).