public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the regulator tree
Date: Tue, 2 Oct 2018 14:02:14 +0100	[thread overview]
Message-ID: <20181002130214.GA6338@sirena.org.uk> (raw)
In-Reply-To: <20181002064317.GD9389@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 300 bytes --]

On Tue, Oct 02, 2018 at 09:43:17AM +0300, Matti Vaittinen wrote:

> tree is correct way to go, right? I'll prepare one against Mark's branch
> "origin/topic/bd718xx". Mark, please let me know if you want me to send
> it or if I should do it on top of some other branch.

That branch is good, thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-02 13:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  3:07 linux-next: build warning after merge of the regulator tree Stephen Rothwell
2018-10-02  6:16 ` Matti Vaittinen
2018-10-02  6:25   ` Stephen Rothwell
2018-10-02  6:43     ` Matti Vaittinen
2018-10-02 13:02       ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-23  4:52 Stephen Rothwell
2024-10-23  4:51 Stephen Rothwell
2020-01-10  2:41 Stephen Rothwell
2016-04-18  3:43 Stephen Rothwell
2016-04-18  9:15 ` Mark Brown
2015-10-07  2:45 Stephen Rothwell

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=20181002130214.GA6338@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.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