Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: "Liang, Prike" <Prike.Liang@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alex Deucher <alexdeucher@gmail.com>,
	"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: linux-next: build warning after merge of the amdgpu tree
Date: Fri, 16 Apr 2021 05:47:03 +0000
Message-ID: <BYAPR12MB3238224BD17317FCC2975CFBFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210416140848.6f458345@canb.auug.org.au>

[AMD Public Use]

> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Sent: Friday, April 16, 2021 12:09 PM
> To: Liang, Prike <Prike.Liang@amd.com>
> Cc: Alex Deucher <alexdeucher@gmail.com>; S-k, Shyam-sundar <Shyam-
> sundar.S-k@amd.com>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>; Linux Next Mailing List <linux-next@vger.kernel.org>
> Subject: Re: linux-next: build warning after merge of the amdgpu tree
>
> Hi,
>
> On Fri, 16 Apr 2021 03:12:12 +0000 "Liang, Prike" <Prike.Liang@amd.com>
> wrote:
> >
> > Hi, Rothwell
>
> (Stephen, actually :-))
>
> > This fix solution hasn't locked down and still being discussed and roll-
> updated in the NVMe mail group.
> > Will update the patch once it refined done.
>
> In which case, this patch should not be in linux-next (or any branch that is
> included by linux-next).
>
How about revert the patch temporally ? Once lock down the solution and will land in the final latest patch.
> --
> Cheers,
> Stephen Rothwell

  reply index

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  2:40 Stephen Rothwell
2021-04-16  3:12 ` Liang, Prike
2021-04-16  4:08   ` Stephen Rothwell
2021-04-16  5:47     ` Liang, Prike [this message]
2021-04-16  5:51       ` Alex Deucher
2021-04-21  6:40 ` Stephen Rothwell
2021-04-23 20:36   ` Alex Deucher
2021-04-23 22:39     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-06-05  2:26 Stephen Rothwell
2021-06-05 14:39 ` Eric Huang
2021-06-03  9:22 Stephen Rothwell
2021-05-28  1:50 Stephen Rothwell
2021-05-04 23:39 Stephen Rothwell
     [not found] ` <DM4PR12MB5133E6A99840D1E8542C0D23F7599@DM4PR12MB5133.namprd12.prod.outlook.com>
2021-05-05  2:55   ` Stephen Rothwell
2021-04-26 12:40 Stephen Rothwell
2021-04-26 14:40 ` Nirmoy
2021-03-24  6:48 Stephen Rothwell
2021-03-24  2:33 Stephen Rothwell
2021-03-22  6:00 Stephen Rothwell
2021-04-21  6:15 ` Stephen Rothwell
2021-03-11 11:00 Stephen Rothwell
2021-04-21  6:10 ` Stephen Rothwell
2021-03-09  2:55 Stephen Rothwell
2021-03-03  6:00 Stephen Rothwell
2021-02-23 23:48 Stephen Rothwell
2021-01-18  5:29 Stephen Rothwell
2021-01-18  5:56 ` Huang, Ray
2021-01-18  6:52   ` Stephen Rothwell
2021-01-18 12:35     ` Huang Rui
2021-01-15  1:00 Stephen Rothwell
2021-01-20  6:15 ` Stephen Rothwell
2021-01-21  0:53   ` Stephen Rothwell
2021-01-21  3:07     ` Alex Deucher
2021-01-21  8:32       ` Daniel Vetter
2020-11-17  4:45 Stephen Rothwell
2020-12-14 19:56 ` Stephen Rothwell
2020-12-15  2:49   ` Stephen Rothwell
2020-04-23  2:24 Stephen Rothwell
2020-03-13  9:57 Stephen Rothwell
2020-02-04 22:44 Stephen Rothwell
2019-12-18 23:18 Stephen Rothwell
2019-11-08  0:21 Stephen Rothwell
2019-07-02  3:53 Stephen Rothwell
2019-05-10  0:59 Stephen Rothwell
2019-05-31  1:27 ` 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=BYAPR12MB3238224BD17317FCC2975CFBFB4C9@BYAPR12MB3238.namprd12.prod.outlook.com \
    --to=prike.liang@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git