All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
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>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Santosh Yaraganavi <santosh.sy@samsung.com>,
	Vinayak Holikatti <h.vinayak@samsung.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Seungwon Jeon <essuuj@gmail.com>
Subject: Re: linux-next: Tree for Jul 20 (scsi/ufs/exynos)
Date: Mon, 20 Jul 2020 09:41:09 -0700	[thread overview]
Message-ID: <e6112633-61c9-fa80-8479-fe90bb360868@infradead.org> (raw)
In-Reply-To: <20200720194225.17de9962@canb.auug.org.au>

On 7/20/20 2:42 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20200717:
> 

on x86_64:

WARNING: unmet direct dependencies detected for PHY_SAMSUNG_UFS
  Depends on [n]: OF [=n] && (ARCH_EXYNOS || COMPILE_TEST [=y])
  Selected by [y]:
  - SCSI_UFS_EXYNOS [=y] && SCSI_LOWLEVEL [=y] && SCSI [=y] && SCSI_UFSHCD_PLATFORM [=y] && (ARCH_EXYNOS || COMPILE_TEST [=y])


There are no build errors since <linux/of.h> provides stubs for
functions when CONFIG_OF is not enabled.

But new warnings are not OK.

thanks.
-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

  parent reply	other threads:[~2020-07-20 16:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  9:42 linux-next: Tree for Jul 20 Stephen Rothwell
2020-07-20 15:51 ` linux-next: Tree for Jul 20 (kernel/bpf/net_namespace) Randy Dunlap
2020-07-20 18:49   ` Stephen Rothwell
2020-07-20 19:37     ` Alexei Starovoitov
2020-07-21 10:19       ` Jakub Sitnicki
2020-07-20 16:29 ` linux-next: Tree for Jul 20 (drivers/gpu/drm/bridge/sil-sii8620.o) Randy Dunlap
2020-07-20 16:29   ` Randy Dunlap
2020-07-20 16:41 ` Randy Dunlap [this message]
2020-07-21 17:41   ` linux-next: Tree for Jul 20 (scsi/ufs/exynos) Alim Akhtar
2020-09-09 20:04     ` Randy Dunlap
2020-09-10  2:27       ` Martin K. Petersen
2020-09-10  2:33         ` Alim Akhtar
2020-07-20 16:56 ` linux-next: Tree for Jul 20 (arch/x86/kvm/) Randy Dunlap
2020-07-20 18:43   ` Stephen Rothwell
2020-07-20 19:59     ` Paul E. McKenney

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=e6112633-61c9-fa80-8479-fe90bb360868@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alim.akhtar@samsung.com \
    --cc=essuuj@gmail.com \
    --cc=h.vinayak@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=santosh.sy@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.