From: "Jangsub Yi" <jangsub.yi@samsung.com>
To: "'Christoph Hellwig'" <hch@infradead.org>
Cc: <ulf.hansson@linaro.org>, <linux-mmc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <junwoo80.lee@samsung.com>,
<sh8267.baek@samsung.com>, <wkon.kim@samsung.com>
Subject: RE: [PATCH] mmc: Add config_host callback to set a mmc queue
Date: Tue, 10 Dec 2024 15:20:59 +0900 [thread overview]
Message-ID: <023901db4acb$adfb84c0$09f28e40$@samsung.com> (raw)
In-Reply-To: <Z1fRaeTMz241A8FN@infradead.org>
> On Tue, Dec 10, 2024 at 02:23:55PM +0900, Jangsub Yi wrote:
> > This is necessary to have separate policies for each device.
> > I will also implement the host modifications related to this content
> > and try to upstream it. Please review the core modifications.
>
> It is not reviewable without a user and your insistance to waste everyones
> time for a patch that as is adds dead code is highly offensive. Stop it.
>
I'm sorry but I couldn't understand your intention clearly because
it's my first time reflecting on the mainline. I will include the
modifications
made to the host (user) and upload the review again.
prev parent reply other threads:[~2024-12-10 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241106051403epcas1p29e983006930bd7b8364b1a1f858ad21c@epcas1p2.samsung.com>
2024-11-06 5:13 ` [PATCH] mmc: Add config_host callback to set a mmc queue Jangsub Yi
2024-11-07 6:30 ` Christoph Hellwig
2024-11-07 9:06 ` ???
2024-11-07 15:11 ` 'Christoph Hellwig'
2024-11-11 8:06 ` Jangsub Yi
2024-12-10 5:23 ` Jangsub Yi
2024-12-10 5:28 ` 'Christoph Hellwig'
2024-12-10 6:20 ` Jangsub Yi [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='023901db4acb$adfb84c0$09f28e40$@samsung.com' \
--to=jangsub.yi@samsung.com \
--cc=hch@infradead.org \
--cc=junwoo80.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sh8267.baek@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wkon.kim@samsung.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