From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: myungjoo.ham@gmail.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Leonard Crestez <leonard.crestez@nxp.com>
Subject: Re: linux-next: build warning after merge of the devfreq tree
Date: Wed, 28 Aug 2019 11:06:41 +0200 [thread overview]
Message-ID: <1642617.PhSKYY5FVN@kreacher> (raw)
In-Reply-To: <CAJ0PZbRvDMW2EApVJ1aaP4O9P3SQTs6Urysm3g-89NrfvVqP-g@mail.gmail.com>
On Monday, August 26, 2019 2:46:08 PM CEST MyungJoo Ham wrote:
> Thank you for pointing this out!
>
> I've added a fix to the tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git/log/?h=for-next
> (and shared the patch in a previous reply)
>
> Rafael, could you please pull the fix from the git repo above?
Done, thanks!
prev parent reply other threads:[~2019-08-28 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 11:50 linux-next: build warning after merge of the devfreq tree Stephen Rothwell
2019-08-26 12:37 ` Leonard Crestez
2019-08-26 12:43 ` [PATCH] PM / devfreq: passive: fix compiler warning MyungJoo Ham
2019-08-26 12:46 ` linux-next: build warning after merge of the devfreq tree MyungJoo Ham
2019-08-28 9:06 ` Rafael J. Wysocki [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=1642617.PhSKYY5FVN@kreacher \
--to=rjw@rjwysocki.net \
--cc=leonard.crestez@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
--cc=sfr@canb.auug.org.au \
/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