From: Dan Carpenter <dan.carpenter@linaro.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: "Linux-Next Mailing List" <linux-next@vger.kernel.org>,
linux-mips@vger.kernel.org, linux-staging@lists.linux.dev,
"Oliver Crumrine" <ozlinux@hotmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: next: mips: cavium_octeon_defconfig failed - drivers/staging/octeon/ethernet.c:204:37: error: storage size of 'rx_status' isn't known
Date: Fri, 29 Sep 2023 17:43:41 +0300 [thread overview]
Message-ID: <b2da789f-af96-4269-bd5c-54d4cb6f05eb@kadam.mountain> (raw)
In-Reply-To: <511073d8-3292-4914-9bcc-8c9acefe3b9a@kadam.mountain>
On Fri, Sep 29, 2023 at 05:39:46PM +0300, Dan Carpenter wrote:
> On Fri, Sep 29, 2023 at 05:18:31PM +0300, Dan Carpenter wrote:
> > This is weird.
> >
> > I managed to reproduce this once but couldn't reproduce it again after
> > that. It seems like an intermittent thing to me.
>
> Nope. I'm just dumb.
>
> Commit b33a296d8311 ("staging: octeon: remove typedef in structs
> cvmx_pip_port_status_t and cvmx_pko_port_status_t") updated
> drivers/staging/octeon/octeon-stubs.h but didn't update
> arch/mips/include/asm/octeon/cvmx-pip.h.
>
> I can send a patch for that.
Actually, perhaps we should just revert the patch? Staging patches
aren't supposed to touch outside of the staging directory.
regards,
dan carpenter
next prev parent reply other threads:[~2023-09-29 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 7:03 next: mips: cavium_octeon_defconfig failed - drivers/staging/octeon/ethernet.c:204:37: error: storage size of 'rx_status' isn't known Naresh Kamboju
2023-09-29 14:18 ` Dan Carpenter
2023-09-29 14:39 ` Dan Carpenter
2023-09-29 14:43 ` Dan Carpenter [this message]
2023-09-29 14:45 ` Dan Carpenter
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=b2da789f-af96-4269-bd5c-54d4cb6f05eb@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=ozlinux@hotmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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