From: Julia Lawall <julia.lawall@lip6.fr>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: linux-arm-kernel@lists.infradead.org,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-aspeed@lists.ozlabs.org, kernel-janitors@vger.kernel.org,
linux-mmc <linux-mmc@vger.kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
Joel Stanley <joel@jms.id.au>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH -next] mmc: aspeed: Fix return value check in aspeed_sdc_probe()
Date: Tue, 27 Aug 2019 08:47:04 +0800 (CST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908270845410.2537@hadrien> (raw)
In-Reply-To: <629128e7-cc91-412f-8946-668fac2eb3b9@www.fastmail.com>
On Tue, 27 Aug 2019, Andrew Jeffery wrote:
>
>
> On Mon, 26 Aug 2019, at 22:34, Dan Carpenter wrote:
> > > Fixes: 09eed7fffd33 ("mmc: Add support for the ASPEED SD controller")
> > ^^^^
> > When we're adding new files, could we use the prefix for the new driver
> > instead of just the subsystem? "mmc: aspeed: Add new driver"?
> > Otherwise it's tricky to know what people want for the driver.
>
> I don't have any issue with the request, but I don't understand this last
> bit. What do you mean by "it's tricky to know what people want for the
> driver"?
There is no obvious algorithm that tells how to go from a file name to an
appropriate subject line prefix.
julia
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-27 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 12:00 [PATCH -next] mmc: aspeed: Fix return value check in aspeed_sdc_probe() Wei Yongjun
2019-08-26 13:03 ` Dan Carpenter
2019-08-26 23:37 ` Andrew Jeffery
2019-08-27 0:47 ` Julia Lawall [this message]
2019-08-27 13:49 ` Ulf Hansson
2019-08-26 23:40 ` Andrew Jeffery
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=alpine.DEB.2.21.1908270845410.2537@hadrien \
--to=julia.lawall@lip6.fr \
--cc=adrian.hunter@intel.com \
--cc=andrew@aj.id.au \
--cc=dan.carpenter@oracle.com \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=weiyongjun1@huawei.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