public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Richard Weinberger <richard@nod.at>,
	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 17:55:08 +0100	[thread overview]
Message-ID: <54C7C2EC.7010605@ahsoftware.de> (raw)
In-Reply-To: <20150127142120.GA3351@pd.tnic>

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

  reply	other threads:[~2015-01-27 16:55 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
2015-01-27 12:44           ` Alexander Holler
2015-01-27 14:21             ` Borislav Petkov
2015-01-27 16:55               ` Alexander Holler [this message]
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=54C7C2EC.7010605@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=bp@alien8.de \
    --cc=chris@printf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=richard@nod.at \
    --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