[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C7C2EC.7010605@ahsoftware.de>
Date: Tue, 27 Jan 2015 17:55:08 +0100
From: Alexander Holler <holler@...oftware.de>
To: Borislav Petkov <bp@...en8.de>
CC: Richard Weinberger <richard@....at>, linux-mmc@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Chris Ball <chris@...ntf.net>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH] mmc: print message if a card supports secure erase/trim
Am 27.01.2015 um 15:21 schrieb Borislav Petkov:
> On Tue, Jan 27, 2015 at 01:44:15PM +0100, Alexander Holler wrote:
>> Yes. Sorry, but I had so many bad experiences with maintainers.
>
> Well, I can't comment on your experience for the simple reason that I
> haven't followed those discussions. In their defence, though, you have
> to know that those people get to review your code, apply it and then
> deal with it long after you've gone on about doing other things.
>
> So, even if you don't always agree with them, you need to realize that
> those are the people responsible for that code and if they request a
> reasonable change in your submission, you have to do it. It is that
> simple.
Totally wrong. I'm free to just stop discussion. That's the difference
between the old type of os communites and corporates where people do
what they've got instructed from above without discussion. I offered
something and wasn't paid to do something.
It was worth a try but I don't have to build a framework to achieve
something simple just because a maintainer requests it.
> [ Unless you have a good argument against it but that's a different
> story and this is what is called the "review" process. ]
I want to see the mentionend information and want that it is seen and do
not want to hide it away deep in the sysfs where it actually must be
searched.
Regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists