linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
	Thierry Reding <treding@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the tegra tree
Date: Wed, 6 Oct 2021 21:27:00 +0300	[thread overview]
Message-ID: <2ed5e10f-7415-4de5-bc2d-a189b78660bd@gmail.com> (raw)
In-Reply-To: <YV3kQPYVKraegCf5@orome.fritz.box>

06.10.2021 21:00, Thierry Reding пишет:
...
>>> Presumably caused by commit
>>>
>>>   bbe30ae68d14 ("cpuidle: tegra: Enable compile testing")
>>>
>>> I have used the tegra tree from next-20211001 for today.
>>>
>>
>> Stephen, thank you. Now I recall what was the actual reason for my
>> version of the patch [1]. Thierry, please use my original patch, thanks.
>>
>> [1]
>> https://patchwork.ozlabs.org/project/linux-tegra/patch/20210912202907.28471-5-digetx@gmail.com/
> 
> Sorry, I forgot to reply to this yesterday. I found a simpler fix for
> this and I pushed that yesterday. Today's linux-next didn't have the
> build failure anymore, so I guess it worked.

It works, thanks.

  reply	other threads:[~2021-10-06 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 23:39 Stephen Rothwell
2021-10-04 23:54 ` Dmitry Osipenko
2021-10-06 18:00   ` Thierry Reding
2021-10-06 18:27     ` Dmitry Osipenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-10 22:51 Stephen Rothwell
2020-05-12 21:12 ` Thierry Reding

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=2ed5e10f-7415-4de5-bc2d-a189b78660bd@gmail.com \
    --to=digetx@gmail.com \
    --cc=ccross@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.com \
    --subject='Re: linux-next: build failure after merge of the tegra tree' \
    /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

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).