linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Johan Hovold <johan@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pavel Machek <pavel@ucw.cz>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: add missing includes to header files
Date: Mon, 24 Jul 2017 15:01:59 +0200	[thread overview]
Message-ID: <20170724130159.GI2729@localhost> (raw)
In-Reply-To: <20170706151607.GC23750@n2100.armlinux.org.uk>

On Thu, Jul 06, 2017 at 04:16:07PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 04, 2017 at 03:25:40PM +0200, Johan Hovold wrote:
> > Add two missing include directives to two header files to avoid
> > compile breakage when the required symbols have not already been
> > defined.
> > 
> > The missing SCU include broke compilation of the (not-yet-merged)
> > suspend support for am335x when !CONFIG_HAVE_ARM_SCU for example:
> > 
> > 	https://lkml.kernel.org/r/20170704131441.GH27842@localhost
> 
> These look reasonable, please send them to the patch system for merging
> after this merge window, thanks.

These two are now in your patch tracker (since a week).

Thanks,
Johan

      reply	other threads:[~2017-07-24 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 13:25 [PATCH 0/2] ARM: add missing includes to header files Johan Hovold
2017-07-04 13:25 ` [PATCH 1/2] ARM: scu: add missing errno include Johan Hovold
2017-07-04 13:25 ` [PATCH 2/2] ARM: pm: add missing types include Johan Hovold
2017-07-05 16:01   ` Pavel Machek
2017-07-06 15:16 ` [PATCH 0/2] ARM: add missing includes to header files Russell King - ARM Linux
2017-07-24 13:01   ` Johan Hovold [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=20170724130159.GI2729@localhost \
    --to=johan@kernel.org \
    --cc=d-gerlach@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=tony@atomide.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).