All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sven Peter <sven@svenpeter.dev>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	asahi@lists.linux.dev, Hector Martin <marcan@marcan.st>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] apple rtkit: add support for atomic operations
Date: Sat, 17 Sep 2022 12:21:51 +0100	[thread overview]
Message-ID: <YyWtz4u5fcxQAB4R@shell.armlinux.org.uk> (raw)
In-Reply-To: <19191d4d-e8a8-4319-bf7b-d5301a792a21@www.fastmail.com>

On Sat, Sep 17, 2022 at 12:42:30PM +0200, Sven Peter wrote:
> Hi,
> 
> On Wed, Sep 14, 2022, at 10:34, Russell King (Oracle) wrote:
> > Hi,
> >
> > This series adds support to the Apple rtkit for atomic messaging,
> > which will be necessary for SMC support on these platforms.
> >
> > SMC support requires a bit of rework after recent review comments,
> > so I'm sending this separately in the hope that we can move forward
> > with upstream kernels.
> 
> Maybe I misremember or maybe you forgot to pick up my reviewed-by tags
> for the mailbox commits.

It's the first time I've sent the mailbox commits after Hector
mentioned them.

> Either way, for the entire series:
> 
> Reviewed-by: Sven Peter <sven@svenpeter.dev>
> 
> 
> We'd usually take the last soc/rtkit commit through the Asahi platform and then the
> soc tree. Taking it through the mailbox tree will make things more complicated
> if SMC (which is the only driver that uses the poll API and hard depends on it) is
> also ready for this merge window. I don't think that's very likely so taking it
> through mailbox is also fine.

I'm sending these seperately because I don't think the platform/mfd
issues will be sorted before the merge window. We've fallen into the
trap where I have a load of updates to the patches in my git tree
that aren't in the Asahi tree, but Lee wants some substantial changes
to the way the MFD part is handled which I think Hector needs to do.
So somehow I need to get my changes back to Hector (I don't do github)
which basically means digging out the original patches from the Asahi
kernel tree and supplying diffs to Hector for those - along with all
the acks/reviewed-bys etc. This *really* isn't nice.

I didn't follow that discussion very well - with about 130 messages
in total in that thread, it just became too much for me to keep track
of, as I explained as the discussion drew to a close. That was the
whole reason for me sending v2, which essentially mostly got ignored
and discussion continued on v1.

So, basically, trying to get these patches into mainline has created
a hell of a lot of extra work and difficulty - and at this point I'm
wondering whether it really is a good idea to continue with this.

It's fine if the comments are all minor issues that can be quickly
resolved, but a major restructuring is a completely different matter.

So, to at least get some progress, I decided to send what would be
possible to hopefully merge during the remainder of this window.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Sven Peter <sven@svenpeter.dev>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	asahi@lists.linux.dev, Hector Martin <marcan@marcan.st>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] apple rtkit: add support for atomic operations
Date: Sat, 17 Sep 2022 12:21:51 +0100	[thread overview]
Message-ID: <YyWtz4u5fcxQAB4R@shell.armlinux.org.uk> (raw)
In-Reply-To: <19191d4d-e8a8-4319-bf7b-d5301a792a21@www.fastmail.com>

On Sat, Sep 17, 2022 at 12:42:30PM +0200, Sven Peter wrote:
> Hi,
> 
> On Wed, Sep 14, 2022, at 10:34, Russell King (Oracle) wrote:
> > Hi,
> >
> > This series adds support to the Apple rtkit for atomic messaging,
> > which will be necessary for SMC support on these platforms.
> >
> > SMC support requires a bit of rework after recent review comments,
> > so I'm sending this separately in the hope that we can move forward
> > with upstream kernels.
> 
> Maybe I misremember or maybe you forgot to pick up my reviewed-by tags
> for the mailbox commits.

It's the first time I've sent the mailbox commits after Hector
mentioned them.

> Either way, for the entire series:
> 
> Reviewed-by: Sven Peter <sven@svenpeter.dev>
> 
> 
> We'd usually take the last soc/rtkit commit through the Asahi platform and then the
> soc tree. Taking it through the mailbox tree will make things more complicated
> if SMC (which is the only driver that uses the poll API and hard depends on it) is
> also ready for this merge window. I don't think that's very likely so taking it
> through mailbox is also fine.

I'm sending these seperately because I don't think the platform/mfd
issues will be sorted before the merge window. We've fallen into the
trap where I have a load of updates to the patches in my git tree
that aren't in the Asahi tree, but Lee wants some substantial changes
to the way the MFD part is handled which I think Hector needs to do.
So somehow I need to get my changes back to Hector (I don't do github)
which basically means digging out the original patches from the Asahi
kernel tree and supplying diffs to Hector for those - along with all
the acks/reviewed-bys etc. This *really* isn't nice.

I didn't follow that discussion very well - with about 130 messages
in total in that thread, it just became too much for me to keep track
of, as I explained as the discussion drew to a close. That was the
whole reason for me sending v2, which essentially mostly got ignored
and discussion continued on v1.

So, basically, trying to get these patches into mainline has created
a hell of a lot of extra work and difficulty - and at this point I'm
wondering whether it really is a good idea to continue with this.

It's fine if the comments are all minor issues that can be quickly
resolved, but a major restructuring is a completely different matter.

So, to at least get some progress, I decided to send what would be
possible to hopefully merge during the remainder of this window.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

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

  reply	other threads:[~2022-09-17 11:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  8:34 [PATCH 0/3] apple rtkit: add support for atomic operations Russell King (Oracle)
2022-09-14  8:34 ` Russell King (Oracle)
2022-09-14  8:34 ` [PATCH 1/3] mailbox: apple: Implement flush() operation Russell King
2022-09-14  8:34   ` Russell King
2022-09-14  8:34 ` [PATCH 2/3] mailbox: apple: Implement poll_data() operation Russell King
2022-09-14  8:34   ` Russell King
2022-09-14  8:34 ` [PATCH 3/3] soc: apple: rtkit: Add apple_rtkit_poll Russell King
2022-09-14  8:34   ` Russell King
2022-09-17 10:42 ` [PATCH 0/3] apple rtkit: add support for atomic operations Sven Peter
2022-09-17 10:42   ` Sven Peter
2022-09-17 11:21   ` Russell King (Oracle) [this message]
2022-09-17 11:21     ` Russell King (Oracle)
2022-09-17 11:33     ` Sven Peter
2022-09-17 11:33       ` Sven Peter
2022-09-17 11:46       ` Russell King (Oracle)
2022-09-17 11:46         ` Russell King (Oracle)
2022-09-17 16:07         ` Jassi Brar
2022-09-17 16:07           ` Jassi Brar
2022-09-17 16:18           ` Russell King (Oracle)
2022-09-17 16:18             ` Russell King (Oracle)
2022-09-17 17:23             ` Jassi Brar
2022-09-17 17:23               ` Jassi Brar
2022-09-17 17:47             ` Hector Martin
2022-09-17 17:47               ` Hector Martin

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=YyWtz4u5fcxQAB4R@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=alyssa@rosenzweig.io \
    --cc=asahi@lists.linux.dev \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marcan@marcan.st \
    --cc=sven@svenpeter.dev \
    /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.