From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
"'Stephen Rothwell'" <sfr@canb.auug.org.au>,
"'Linux Next Mailing List'" <linux-next@vger.kernel.org>,
"'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>,
"'Seungwon Jeon'" <essuuj@gmail.com>
Subject: Re: linux-next: Tree for Jul 20 (scsi/ufs/exynos)
Date: Wed, 09 Sep 2020 22:27:36 -0400 [thread overview]
Message-ID: <yq1a6xy2wph.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <f72b8022-1ebd-c5a1-2fe2-a3e93854fd0e@infradead.org> (Randy Dunlap's message of "Wed, 9 Sep 2020 13:04:24 -0700")
Randy,
> I am still seeing this in linux-next of 20200909.
> Was there a patch posted that I missed and is not applied anywhere yet?
This patch became a victim of dropping the Exynos changes in 5.9. I have
added it back in.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-09-10 2:30 UTC|newest]
Thread overview: 14+ 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:41 ` linux-next: Tree for Jul 20 (scsi/ufs/exynos) Randy Dunlap
2020-07-21 17:41 ` Alim Akhtar
2020-09-09 20:04 ` Randy Dunlap
2020-09-10 2:27 ` Martin K. Petersen [this message]
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=yq1a6xy2wph.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--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=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).