public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
	Christoph Hellwig <hch@lst.de>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: linux-next: manual merge of the generic-ioremap tree with the drivers-x86 tree
Date: Tue, 28 Jan 2020 21:06:15 +1100	[thread overview]
Message-ID: <20200128210615.4347a362@canb.auug.org.au> (raw)
In-Reply-To: <CAHp75VctM6DBpDFj0eXUo4ipawCpfDgqexBHwjQGQpomjY2YDQ@mail.gmail.com>

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

Hi Andy,

On Tue, 28 Jan 2020 11:11:32 +0200 Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> I can't reproduce this. Linus already pulled PR for PDx86,
> 
> $ git checkout -b test-xxx origin/master
> Branch 'test-xxx' set up to track remote branch 'master' from 'origin'.
> Switched to a new branch 'test-xxx'
> $ git merge for-next
> Already up to date.

Thanks for letting me know.  Sorry about the noise.

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2020-01-28 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  5:15 linux-next: manual merge of the generic-ioremap tree with the drivers-x86 tree Stephen Rothwell
2020-01-27 23:03 ` Stephen Rothwell
2020-01-28  9:11   ` Andy Shevchenko
2020-01-28 10:06     ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-10  5:52 Stephen Rothwell
2020-01-10 10:22 ` Andy Shevchenko
2020-01-27 22:56 ` 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=20200128210615.4347a362@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andy.shevchenko@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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