From: Richard Weinberger <richard@nod.at>
To: Alexander Holler <holler@ahsoftware.de>, Borislav Petkov <bp@alien8.de>
Cc: linux-mmc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Chris Ball <chris@printf.net>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH] mmc: print message if a card supports secure erase/trim
Date: Tue, 27 Jan 2015 13:31:32 +0100 [thread overview]
Message-ID: <54C78524.3070901@nod.at> (raw)
In-Reply-To: <54C7816A.8050800@ahsoftware.de>
Am 27.01.2015 um 13:15 schrieb Alexander Holler:
> Am 27.01.2015 um 13:08 schrieb Borislav Petkov:
>> On Tue, Jan 27, 2015 at 01:02:49PM +0100, Alexander Holler wrote:
>>> Look at the source at the message which is printed just before and decide
>>> which one you find more informational / useful.
>>
>> I find such a message absolutely useless. Also, if it flies off and
>> printk buffer gets overwritten, it serves you sh*t. IOW, listen to what
>> Richard tells you.
>
> Ok. I shut/give up.
There is no need to be sulky.
> Maybe you could be so nice to inform me where the similiar detail is exposed in sysfs for SSDs.
If it is not already exposed and you can come up with a sane use case send a patch.
> Also it's unlikely I will send any further patch. There are still 21 from me where I've exposed sysfs attributes for NAND devices which are still not applied and most NAND devices
> still don't have a sysfs entry.
>
> So why should I waste my time again?
If you give up after the first review round there is nothing I can do for you.
Postings like https://lkml.org/lkml/2014/5/30/162 are also not really beneficial
to get a patch merged.
Thanks,
//richard
P.s. If you see every not-merged patch as a waste of time, please stop developing software as
it is obviously not an enjoyment for you.
next prev parent reply other threads:[~2015-01-27 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 11:48 [PATCH] mmc: print message if a card supports secure erase/trim Alexander Holler
2015-01-27 11:55 ` Richard Weinberger
2015-01-27 12:02 ` Alexander Holler
2015-01-27 12:06 ` Richard Weinberger
2015-01-27 18:56 ` Joe Perches
2015-01-27 12:08 ` Borislav Petkov
2015-01-27 12:15 ` Alexander Holler
2015-01-27 12:31 ` Richard Weinberger [this message]
2015-01-27 12:44 ` Alexander Holler
2015-01-27 14:21 ` Borislav Petkov
2015-01-27 16:55 ` Alexander Holler
2015-01-27 17:24 ` Steven Rostedt
2015-01-27 17:38 ` Alexander Holler
2015-01-27 17:48 ` Steven Rostedt
2015-01-27 18:13 ` Alexander Holler
2015-01-27 18:21 ` Steven Rostedt
2015-01-27 18:33 ` Alexander Holler
2015-01-27 18:42 ` Steven Rostedt
2015-01-27 19:14 ` Alexander Holler
2015-01-27 17:53 ` Arend van Spriel
2015-01-27 18:04 ` Alexander Holler
2015-01-27 18:09 ` Richard Weinberger
2015-01-27 18:12 ` Borislav Petkov
2015-01-27 12:20 ` Arend van Spriel
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=54C78524.3070901@nod.at \
--to=richard@nod.at \
--cc=bp@alien8.de \
--cc=chris@printf.net \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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