linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Nathan Chancellor <nathan@kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Palmer Dabbelt <palmer@rivosinc.com>, Guo Ren <guoren@kernel.org>
Subject: Re: [PATCH] tools: Fixed MIPS builds due to struct flock re-definition
Date: Tue, 19 Jul 2022 14:17:47 -0700	[thread overview]
Message-ID: <e790fbe4-aa9c-a5a4-d445-1c4cad8e93e2@gmail.com> (raw)
In-Reply-To: <CAK8P3a1LnCz32DixQ2VuBh+c64+CNqNJ8v2Nk0X6P8kYA4=-gQ@mail.gmail.com>



On 7/19/2022 2:15 PM, Arnd Bergmann wrote:
> On Tue, Jul 19, 2022 at 9:05 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>> On 7/19/2022 12:42 AM, Arnd Bergmann wrote:
> 
>>> I applied this to the asm-generic tree, but now I'm having second thoughts, as
>>> this only changes the tools/include/ version but not the version we ship to user
>>> space. Normally these are meant to be kept in sync.
>>
>> Thanks! Just to be clear, applying just your patch is not enough as the
>> original build issue is still present, so we would need my change plus
>> yours, I think that is what you intended but just wanted to double
>> confirm.
> 
> Yes, this was just the diff on top of your patch, I've folded it into a single
> commit now.
> 
>> On a side note your tree at:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git/refs/heads
>>
>> does not appear to have it included/pushed out yet, should I be looking
>> at another git tree?
> 
> Pushed it out now. There is the main asm-generic branch that is in
> linux-next, and the asm-generic-fixes branch that I should send after
> the build bots report success.
> 
> I've merged the fixes branch into the main branch for testing for the
> moment, but will undo the merge when I forward the contents.

All good, thanks a lot!
-- 
Florian

      reply	other threads:[~2022-07-19 21:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 18:55 [PATCH] tools: Fixed MIPS builds due to struct flock re-definition Florian Fainelli
2022-07-16 23:21 ` Florian Fainelli
2022-07-19  0:17   ` Florian Fainelli
2022-07-19  4:30 ` Christoph Hellwig
2022-07-19  7:42 ` Arnd Bergmann
2022-07-19 15:16   ` Christoph Hellwig
2022-07-19 19:05   ` Florian Fainelli
2022-07-19 21:15     ` Arnd Bergmann
2022-07-19 21:17       ` Florian Fainelli [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=e790fbe4-aa9c-a5a4-d445-1c4cad8e93e2@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=hch@lst.de \
    --cc=heiko@sntech.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nathan@kernel.org \
    --cc=palmer@rivosinc.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;
as well as URLs for NNTP newsgroup(s).