All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Richard Weinberger <richard@nod.at>, 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:44:15 +0100	[thread overview]
Message-ID: <54C7881F.6020501@ahsoftware.de> (raw)
In-Reply-To: <54C78524.3070901@nod.at>

Am 27.01.2015 um 13:31 schrieb Richard Weinberger:

>> 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.

Yes. Sorry, but I had so many bad experiences with maintainers. They 
told me that using functions means hiding stuff, that I should bisect 
even when I was absolutely sure which patch was wrong (and everxyone 
could see it by just reading the source and by reading my comments, I've 
got blamed because I prefer a controlled BUG_ON() (which might even just 
kill the involved tasks, depending on config settings) instead of a 
desastrous memory corruption which (hard-) reseted the machine (and 
might have done even more bad things) and so on.

Regards,

Alexander Holler

  reply	other threads:[~2015-01-27 12:44 UTC|newest]

Thread overview: 26+ 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 [this message]
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 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
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=54C7881F.6020501@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.