public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	linux-mmc@vger.kernel.org, linux-usb@vger.kernel.org
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Tony Olech <tony.olech@elandigitalsystems.com>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: mmc: vub300: Use common code in __download_offload_pseudocode()
Date: Tue, 31 Oct 2017 15:42:30 +0000	[thread overview]
Message-ID: <ff32476e-f60f-a672-0e82-c5e69b5ed812@users.sourceforge.net> (raw)
In-Reply-To: <CAPDyKFp7zRLyGR4UfC8A3py8M9ZDi4nyeU8qUSg4NSrwSLh0HA@mail.gmail.com>

> Regarding posts from Markus' I am well aware of the problems.

Interesting …


> In my case, it hasn't been much of a hurdle, I simply ignore changes
> that seems silly to me.

* How often did this happen so far?

* Are any update suggestions left over where a constructive feedback
  will make sense?

Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2017-10-31 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 19:31 [PATCH] mmc: vub300: Use common code in __download_offload_pseudocode() SF Markus Elfring
2017-10-30 11:40 ` Ulf Hansson
2017-10-30 12:15   ` Dan Carpenter
2017-10-30 13:03     ` Ulf Hansson
2017-10-31  8:45       ` Dan Carpenter
2017-10-31  9:15         ` SF Markus Elfring
2017-10-31 15:10         ` [PATCH] " Ulf Hansson
2017-10-31 15:42           ` SF Markus Elfring [this message]

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=ff32476e-f60f-a672-0e82-c5e69b5ed812@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tony.olech@elandigitalsystems.com \
    --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