From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bart Van Assche <bvanassche@acm.org>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:pending-fixes 787/854] arch/sparc/mm/srmmu.c:1662:30: error: 'smpfunc_t' undeclared; did you mean 'cmp_func_t'?
Date: Wed, 5 Oct 2022 08:39:50 +1100 [thread overview]
Message-ID: <20221005083950.03aa686c@canb.auug.org.au> (raw)
In-Reply-To: <13613249-90bb-99d1-8b9a-eb09ed3c200b@acm.org>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Hi Bart,
On Tue, 4 Oct 2022 06:56:38 -0700 Bart Van Assche <bvanassche@acm.org> wrote:
>
> It seems like the pending-fixes branch is missing the following
> commit from the master branch: 17006e86a764 ("sparc: Unbreak the
> build").
That commit is now in Linus' tree (merged overnight my time).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-10-04 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 3:02 kernel test robot
2022-10-04 13:56 ` Bart Van Assche
2022-10-04 21:39 ` Stephen Rothwell [this message]
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=20221005083950.03aa686c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bvanassche@acm.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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