From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
linux-rt-devel@lists.linux.dev, Arnd Bergmann <arnd@arndb.de>,
Linus Walleij <linus.walleij@linaro.org>,
"Yadi.hu" <yadi.hu@windriver.com>, Bryan Brattlof <bb@ti.com>
Subject: Re: [PATCH v4 1/2] ARM: mm: fault: Enable interrupts before invoking __do_user_fault()
Date: Fri, 16 Jan 2026 21:30:02 +0100 [thread overview]
Message-ID: <20260116203002.ocPCBG8L@linutronix.de> (raw)
In-Reply-To: <aWqbB68tx8pdkN2q@shell.armlinux.org.uk>
On 2026-01-16 20:09:43 [+0000], Russell King (Oracle) wrote:
> > Oh, and, as I've said on netdev recently, I have lots of patches. I
> > don't have time to push all patches all the time. Those that I think
> > are the highest priority get the attention - so if something goes
> > quiet, the patches don't get progressed (because something else has
> > taken over.)
> >
> > I haven't published these yet to my external git tree because they're
> > currently on top of my raw private "development" branch containing...
> >
> > $ git lg origin..rmk | wc -l
> > 473
> >
> > many of those behind those I mentioned above. At some point I need to
> > move them to their own separate branch, or to the "misc" branch after
> > sending them to the mailing list... but the latter means spending time
> > writing a covering message summarising the changes, and the key thing
> > is "time".
> >
> > I've wasted almost all of today running a bisect for a stmmac issue that
> > takes out my _entire_ network at home. It's wasted because what I
> > thought was a good commit turns out, on re-testing, to have been bad,
> > and right now I have no idea what a good commit is, and whether that
> > even exists before the platform support was merged.
>
> Sorry for a third reply... yesterday I started at about 10am, finished
> at 2am last night chasing a different stmmac regression.
>
> Yea, if there was more time, then I could push all the patches I have,
> but I don't, and the above patches were generated back when we were
> discussing the issue last time.
No worries. Is your tree rmk tree public so I could pull those and test?
Do you want me to review any of those?
Sebastian
next prev parent reply other threads:[~2026-01-16 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 17:00 [PATCH v4 0/2] ARM: Remaining PREEMPT_RT bits Sebastian Andrzej Siewior
2026-01-16 17:00 ` [PATCH v4 1/2] ARM: mm: fault: Enable interrupts before invoking __do_user_fault() Sebastian Andrzej Siewior
2026-01-16 17:33 ` Russell King (Oracle)
2026-01-16 18:12 ` Sebastian Andrzej Siewior
2026-01-16 20:01 ` Russell King (Oracle)
2026-01-16 20:07 ` Russell King (Oracle)
2026-01-16 20:09 ` Russell King (Oracle)
2026-01-16 20:30 ` Sebastian Andrzej Siewior [this message]
2026-01-16 17:00 ` [PATCH v4 2/2] ARM: Allow to enable RT Sebastian Andrzej Siewior
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=20260116203002.ocPCBG8L@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=arnd@arndb.de \
--cc=bb@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=yadi.hu@windriver.com \
/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