From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
avri.altman@wdc.com, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
scsi <linux-scsi@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v6 0/7] treewide: ufs: Add support for Renesas R-Car UFS controller
Date: Thu, 16 Jun 2022 21:29:59 -0400 [thread overview]
Message-ID: <yq1k09gozdt.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <CAMuHMdVR2=VHUxfDTukDt7rSOPBYCFr3qXQzZNTdkw9Z-jEBkg@mail.gmail.com> (Geert Uytterhoeven's message of "Wed, 15 Jun 2022 09:20:40 +0200")
Geert,
>> OK. Just queued it up in for-next to see what would break. It's not in
>> the actual queue for 5.20.
>
> IC. How will I know when they are queued for real?
I send out merge notifications when patches end up in either 'fixes' or
'queue'.
My 'for-next' branch is ephemeral and I often queue things to just see
what breaks. I do not have the ability to test several of the drivers
that go through my tree so I do depend on the various checkers to help
identify issues prior to merging.
> No need to wait with the rest, unless you are not happy with it yet?
> Thanks!
The rest looks OK to me. I'll leave it in.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-06-17 1:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:05 [PATCH v6 0/7] treewide: ufs: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 1/7] dt-bindings: ufs: Document Renesas R-Car UFS host controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 2/7] ufs: add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 3/7] ufs: add UFSHCD_QUIRK_HIBERN_FASTAUTO Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 4/7] scsi: ufs-renesas: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 5/7] scsi: MAINTAINERS: Add maintainer for Renesas UFS driver Yoshihiro Shimoda
2022-06-03 11:05 ` [PATCH v6 6/7] arm64: dts: renesas: r8a779f0: Add UFS node Yoshihiro Shimoda
2022-06-14 8:02 ` Geert Uytterhoeven
2022-06-03 11:05 ` [PATCH v6 7/7] arm64: dts: renesas: r8a779f0: spider-cpu: Enable UFS device Yoshihiro Shimoda
2022-06-14 8:06 ` Geert Uytterhoeven
2022-06-21 15:14 ` Wolfram Sang
2022-06-22 6:32 ` Avri Altman
2022-06-22 8:38 ` Wolfram Sang
2022-06-22 9:42 ` Avri Altman
2022-06-22 9:47 ` Avri Altman
2022-06-22 11:16 ` Wolfram Sang
2022-06-23 4:20 ` Yoshihiro Shimoda
2022-06-22 8:11 ` Yoshihiro Shimoda
2022-06-22 8:22 ` Wolfram Sang
2022-06-22 8:28 ` Yoshihiro Shimoda
2022-06-14 8:00 ` [PATCH v6 0/7] treewide: ufs: Add support for Renesas R-Car UFS controller Geert Uytterhoeven
2022-06-15 2:53 ` Martin K. Petersen
2022-06-15 7:20 ` Geert Uytterhoeven
2022-06-17 1:29 ` Martin K. Petersen [this message]
2022-06-17 2:21 ` 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=yq1k09gozdt.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jejb@linux.ibm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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
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.