From: Mark Brown <broonie@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
helpdesk@kernel.org
Subject: Re: linux-next: Tree for Jun 10
Date: Thu, 11 Jun 2026 20:29:13 +0100 [thread overview]
Message-ID: <aisMicRreOJ1bcYl@sirena.co.uk> (raw)
In-Reply-To: <f4ca5f0b-a897-4249-8b04-759dc2d10610@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Thu, Jun 11, 2026 at 12:25:17PM -0700, Randy Dunlap wrote:
> On 6/11/26 11:47 AM, Mark Brown wrote:
> > I see kup running and didn't notice any errors, the output is lost to
> > scrollback now. I'm on my laptop rather than my desktop, presumably
> > there's something different though not knowingly. I'm not sure it
> > matters, I don't know that anyone but Randy even looks at the patch
> > files.
> Maybe you should just announce that they are being discontinued.
> It will alter my workflow but I can handle it.
Whatever is up should be resolved whenever I'm back on my desktop on
Monday I'd expect, like I say it's not a deliberate change. I can't
check for differences since the reason I'm using my laptop is that I'm
not near my destkop, and I won't be able to double check for any error
reports from kup until I next try to publish - I did see it running
today, don't think I stared at it until the upload was finished though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-11 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:53 linux-next: Tree for Jun 10 Mark Brown
2026-06-10 22:57 ` Randy Dunlap
2026-06-11 18:24 ` Randy Dunlap
2026-06-11 18:39 ` Konstantin Ryabitsev
2026-06-11 18:47 ` Mark Brown
2026-06-11 19:25 ` Randy Dunlap
2026-06-11 19:29 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-10 6:08 Stephen Rothwell
2022-06-10 5:35 Stephen Rothwell
2021-06-10 9:48 Stephen Rothwell
2020-06-10 9:55 Stephen Rothwell
2015-06-10 11:55 Stephen Rothwell
2014-06-10 6:50 Stephen Rothwell
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=aisMicRreOJ1bcYl@sirena.co.uk \
--to=broonie@kernel.org \
--cc=helpdesk@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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