[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cb86687c-f07c-f484-b4fa-ae73e124a59a@quicinc.com>
Date: Tue, 7 Mar 2023 10:58:57 +0530
From: Md Sadre Alam <quic_mdalam@...cinc.com>
To: Mark Brown <broonie@...nel.org>
CC: <agross@...nel.org>, <andersson@...nel.org>,
<konrad.dybcio@...aro.org>, <linux-arm-msm@...r.kernel.org>,
<linux-spi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<quic_sjaganat@...cinc.com>, <quic_srichara@...cinc.com>,
<quic_varada@...cinc.com>
Subject: Re: [PATCH 2/5] spi: qup: Use
devm_platform_get_and_ioremap_resource()
On 3/6/2023 9:14 PM, Mark Brown wrote:
> On Mon, Mar 06, 2023 at 08:14:04PM +0530, Md Sadre Alam wrote:
>> Convert platform_get_resource(), devm_ioremap_resource() to a single
>> call to devm_platform_get_and_ioremap_resource(), as this is exactly
>> what this function does.
> You've not copied me on the rest of the series so I don't know what's
> going on with dependencies. When sending a patch series it is important
> to ensure that all the various maintainers understand what the
> relationship between the patches as the expecation is that there will be
> interdependencies. Either copy everyone on the whole series or at least
> copy them on the cover letter and explain what's going on. If there are
> no strong interdependencies then it's generally simplest to just send
> the patches separately to avoid any possible confusion.
Thanks for you update. Yes! these all patches are not dependent at all.
So i will send these all patches separately.
Powered by blists - more mailing lists