From: Mark Brown <broonie@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 2
Date: Wed, 3 Aug 2022 12:51:57 +0100 [thread overview]
Message-ID: <YuphXWlnKgTgnE6U@sirena.org.uk> (raw)
In-Reply-To: <d1f90d44-a1e9-7490-f789-f928b85a1d26@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 677 bytes --]
On Wed, Aug 03, 2022 at 08:48:58AM +0700, Bagas Sanjaya wrote:
> What is missing here is powerpc build (ppc64_defconfig), since the
> architecture is often used for cross-compile test.
No, it's not missing. Stephen's native PowerPC build has been
deliberately replaced with a native arm64 defconfig build since that's
the system I have access to and that's who's paying the bills here.
> And I think since we're at merge window for 6.0, we need to say
> "Please do not add material for 6.1 until 6.0-rc1 have been
> released".
Right, I didn't add a note about that. Hopefully people are sensible
enough to figure it out without the explicit statement in the -next
mails.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-03 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 1:03 linux-next: Tree for Aug 2 broonie
2022-08-03 1:48 ` Bagas Sanjaya
2022-08-03 11:51 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 4:24 Stephen Rothwell
2021-08-03 1:24 Mark Brown
2019-08-02 5:52 Stephen Rothwell
2018-08-02 9:31 Stephen Rothwell
2017-08-02 6:38 Stephen Rothwell
2016-08-02 4:06 Stephen Rothwell
2013-08-02 8:04 Stephen Rothwell
2013-08-02 8:04 ` Stephen Rothwell
2012-08-02 4:15 Stephen Rothwell
2011-08-02 5:57 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=YuphXWlnKgTgnE6U@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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.