Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Naga Sureshkumar Relli <nagasure@xilinx.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michal Simek <michals@xilinx.com>,
	linux-spi <linux-spi@vger.kernel.org>,
	YueHaibing <yuehaibing@huawei.com>
Subject: RE: linux-next: Tree for Apr 9 (spi/spi-zynq-qspi.c)
Date: Wed, 10 Apr 2019 05:46:54 +0000
Message-ID: <MWHPR02MB2623DDF884FD2DAA9C4B7C40AF2E0@MWHPR02MB2623.namprd02.prod.outlook.com> (raw)
In-Reply-To: <4c933ec6-0247-5820-dfc2-326a5bc6b227@infradead.org>

Hi Randy,

I have sent the patch on top of the patch sent by yuehaibing@huawei.com.

Thanks,
Naga Sureshkumar Relli

> -----Original Message-----
> From: Randy Dunlap <rdunlap@infradead.org>
> Sent: Tuesday, April 9, 2019 8:52 PM
> To: Stephen Rothwell <sfr@canb.auug.org.au>; Linux Next Mailing List <linux-
> next@vger.kernel.org>
> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Naga Sureshkumar Relli
> <nagasure@xilinx.com>; Michal Simek <michals@xilinx.com>; linux-spi <linux-
> spi@vger.kernel.org>
> Subject: Re: linux-next: Tree for Apr 9 (spi/spi-zynq-qspi.c)
> 
> On 4/9/19 1:00 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190408:
> >
> 
> on x86_64:
> 
> ld: drivers/spi/spi-zynq-qspi.o: in function `zynq_qspi_supports_op':
> spi-zynq-qspi.c:(.text+0x185): undefined reference to `spi_mem_default_supports_op'
> 
> 
> Full randconfig file is attached.
> 
> --
> ~Randy

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  8:00 linux-next: Tree for Apr 9 Stephen Rothwell
2019-04-09 15:21 ` linux-next: Tree for Apr 9 (spi/spi-zynq-qspi.c) Randy Dunlap
2019-04-10  5:46   ` Naga Sureshkumar Relli [this message]
2019-04-09 15:28 ` linux-next: Tree for Apr 9 (arch/x86/platform/efi/efi_64.c) Randy Dunlap
2019-04-09 18:25 ` linux-next: Tree for Apr 9 Guenter Roeck
2019-04-09 18:44   ` Trond Myklebust

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=MWHPR02MB2623DDF884FD2DAA9C4B7C40AF2E0@MWHPR02MB2623.namprd02.prod.outlook.com \
    --to=nagasure@xilinx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=michals@xilinx.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yuehaibing@huawei.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

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