From: "Sarthak Garg (QUIC)" <quic_sartgarg@quicinc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"Ram Prakash Gupta (QUIC)" <quic_rampraka@quicinc.com>,
"Bhaskar Valaboju (QUIC)" <quic_bhaskarv@quicinc.com>,
"Sachin Gupta (QUIC)" <quic_sachgupt@quicinc.com>,
"Pradeep Pragallapati (QUIC)" <quic_pragalla@quicinc.com>,
"Sayali Lokhande (QUIC)" <quic_sayalil@quicinc.com>,
Brian Norris <briannorris@chromium.org>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: RE: [PATCH V1 1/2] mmc: core: Define new vendor ops to enable internal features
Date: Thu, 11 May 2023 05:00:24 +0000 [thread overview]
Message-ID: <c1dc3d77db644958b906fa55200a0ae2@quicinc.com> (raw)
In-Reply-To: <ZDlR9VB7jRxMsEZH@infradead.org>
Thanks for your valuable comments. We didn't ignore the previous comments instead we tried to address most of the comments by trying the suggested alternatives as well but didn't see power improvement as compared to this feature. Moreover we got the intuition that maintainability was the main concern hence we came up with this newer approach of hooks to limit the lines of code in core layer. Every change was pushed earlier in the previous posts and this time we just refactored the code and was about to push the series but as per current discussion we'll be reviving the old discussion and try to close all the comments. Closing this thread now.
> -----Original Message-----
> From: Christoph Hellwig <hch@infradead.org>
> Sent: Friday, April 14, 2023 6:46 PM
> To: Sarthak Garg (QUIC) <quic_sartgarg@quicinc.com>
> Cc: Christoph Hellwig <hch@infradead.org>; adrian.hunter@intel.com;
> ulf.hansson@linaro.org; linux-mmc@vger.kernel.org; linux-
> kernel@vger.kernel.org; linux-arm-msm@vger.kernel.org; Ram Prakash Gupta
> (QUIC) <quic_rampraka@quicinc.com>; Bhaskar Valaboju (QUIC)
> <quic_bhaskarv@quicinc.com>; Sachin Gupta (QUIC)
> <quic_sachgupt@quicinc.com>; Pradeep Pragallapati (QUIC)
> <quic_pragalla@quicinc.com>; Sayali Lokhande (QUIC)
> <quic_sayalil@quicinc.com>; Brian Norris <briannorris@chromium.org>;
> Wolfram Sang <wsa+renesas@sang-engineering.com>; Linus Walleij
> <linus.walleij@linaro.org>
> Subject: Re: [PATCH V1 1/2] mmc: core: Define new vendor ops to enable
> internal features
>
> On Fri, Apr 14, 2023 at 06:52:18AM +0000, Sarthak Garg (QUIC) wrote:
> > Sorry for the confusion by vendor file I meant driver file for Qualcomm SDCC
> controller (sdhci-msm.c).
>
> This is still not how we do development. The two series you've been pointed out
> got valuable feedback that;s been ignored for between one and four years, that
> needs to be followed up with.
>
> You're not going to get magic hooks for your driver that you're not sharing with
> us just because you're too lazy to follow up on the review comments.
next prev parent reply other threads:[~2023-05-11 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 16:57 [PATCH V1 0/2] Introduce new vendor op and export few symbols Sarthak Garg
2023-04-01 16:57 ` [PATCH V1 1/2] mmc: core: Define new vendor ops to enable internal features Sarthak Garg
2023-04-02 12:48 ` Linus Walleij
2023-04-14 5:29 ` Sarthak Garg (QUIC)
2023-04-04 5:13 ` Christoph Hellwig
2023-04-14 5:33 ` Sarthak Garg (QUIC)
2023-04-14 5:36 ` Christoph Hellwig
2023-04-14 6:52 ` Sarthak Garg (QUIC)
2023-04-14 13:15 ` Christoph Hellwig
2023-05-11 5:00 ` Sarthak Garg (QUIC) [this message]
2023-04-01 16:57 ` [PATCH V1 2/2] mmc: core: Export core functions to let vendors use for their features Sarthak Garg
2023-04-01 20:50 ` Heiner Kallweit
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=c1dc3d77db644958b906fa55200a0ae2@quicinc.com \
--to=quic_sartgarg@quicinc.com \
--cc=adrian.hunter@intel.com \
--cc=briannorris@chromium.org \
--cc=hch@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=quic_bhaskarv@quicinc.com \
--cc=quic_pragalla@quicinc.com \
--cc=quic_rampraka@quicinc.com \
--cc=quic_sachgupt@quicinc.com \
--cc=quic_sayalil@quicinc.com \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox