From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Martin K. Petersen'" <martin.petersen@oracle.com>
Cc: "'Randy Dunlap'" <rdunlap@infradead.org>, <avri.altman@wdc.com>,
<linux-scsi@vger.kernel.org>, <sfr@canb.auug.org.au>
Subject: RE: [PATCH -next] scsi: ufs: Fix 'unmet direct dependencies' config warning
Date: Wed, 5 Aug 2020 07:18:31 +0530 [thread overview]
Message-ID: <005e01d66aca$8826f1c0$9874d540$@samsung.com> (raw)
In-Reply-To: <yq1lfitzxgf.fsf@ca-mkp.ca.oracle.com>
> -----Original Message-----
> From: Martin K. Petersen <martin.petersen@oracle.com>
> Sent: 05 August 2020 07:07
> To: Alim Akhtar <alim.akhtar@samsung.com>
> Cc: 'Randy Dunlap' <rdunlap@infradead.org>; martin.petersen@oracle.com;
> avri.altman@wdc.com; linux-scsi@vger.kernel.org; sfr@canb.auug.org.au
> Subject: Re: [PATCH -next] scsi: ufs: Fix 'unmet direct dependencies' config
> warning
>
>
> Alim,
>
> > I don’t see this patch in your tree, let me know if I need to -resend
> > this.
>
> I postponed the Exynos update to 5.10 since there were a few zeroday warnings
> and it looked like the 5.8 release was imminent.
>
I suppose all fixes where sent on time for ufs-exynos driver. Anyway let me know in case
I need to re-send any patches.
The $SUBJECT patch is needed to fix a build warning.
Thank you!
> --
> Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-08-05 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200721174310epcas5p2a448e38c6e4d5e36e9f0417f5ddced6d@epcas5p2.samsung.com>
2020-07-21 17:20 ` [PATCH -next] scsi: ufs: Fix 'unmet direct dependencies' config warning Alim Akhtar
2020-07-21 17:57 ` Randy Dunlap
2020-08-05 1:32 ` Alim Akhtar
2020-08-05 1:37 ` Martin K. Petersen
2020-08-05 1:48 ` Alim Akhtar [this message]
2020-07-22 4:28 ` Martin K. Petersen
2020-09-15 20:16 ` Martin K. Petersen
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='005e01d66aca$8826f1c0$9874d540$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.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
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