From: Vignesh Raghavendra <vigneshr@ti.com>
To: Dhruva Gole <d-gole@ti.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Vaishnav Achath <vaishnav.a@ti.com>,
Apurva Nandan <a-nandan@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, Mark Brown <broonie@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Enable UBIFS
Date: Tue, 9 May 2023 16:14:22 +0530 [thread overview]
Message-ID: <8aae9af7-22ea-4b2b-563c-0f01e361775c@ti.com> (raw)
In-Reply-To: <a25ce95e-126e-7a1a-1bb0-2a3d73ea4aee@ti.com>
On 08/05/23 13:13, Dhruva Gole wrote:
> Hi,
>
> On 17/04/23 14:52, Dhruva Gole wrote:
>> UBIFS is a file system for flash devices which works on top of UBI.
>>
>> Signed-off-by: Dhruva Gole <d-gole@ti.com>
>> ---
>> arch/arm64/configs/defconfig | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>> index 4f59fa575b47..a632d2a1db93 100644
>> --- a/arch/arm64/configs/defconfig
>> +++ b/arch/arm64/configs/defconfig
>> @@ -267,6 +267,8 @@ CONFIG_MTD_NAND_BRCMNAND=m
>> CONFIG_MTD_NAND_FSL_IFC=y
>> CONFIG_MTD_NAND_QCOM=y
>> CONFIG_MTD_SPI_NOR=y
>> +CONFIG_MTD_UBI=m
>> +CONFIG_UBIFS_FS=m
>
> Gentle ping on this patch, can we please pull this in since nobody has
> raised any objections since over 3 weeks?
I am planning to queuing this via TI arch tree, if there no objections.
Unfortunately, your patch landed post v6.4-rc1 PRs were sent out. And
thus will only be part of v6.5 cycle. Note that v6.4-rc1 was tagged last
Monday, so you may have to wait a while for folks to catch up
>
>> CONFIG_BLK_DEV_LOOP=y
>> CONFIG_BLK_DEV_NBD=m
>> CONFIG_VIRTIO_BLK=y
>
--
Regards
Vignesh
prev parent reply other threads:[~2023-05-09 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:22 [PATCH] arm64: defconfig: Enable UBIFS Dhruva Gole
2023-05-08 7:43 ` Dhruva Gole
2023-05-09 10:44 ` Vignesh Raghavendra [this message]
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=8aae9af7-22ea-4b2b-563c-0f01e361775c@ti.com \
--to=vigneshr@ti.com \
--cc=a-nandan@ti.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=d-gole@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=vaishnav.a@ti.com \
--cc=will@kernel.org \
/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).