public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Samuel Iglesias Gonsálvez" <siglesias@igalia.com>,
	industrypack-devel@lists.sourceforge.net,
	"Jens Taprogge" <jens.taprogge@taprogge.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: ipack: Improve a size determination in ipack_bus_register()
Date: Mon, 15 May 2017 06:40:24 +0000	[thread overview]
Message-ID: <161221bf-26a7-6f45-6e2e-b166654aaee8@users.sourceforge.net> (raw)
In-Reply-To: <20170515055653.GA5658@kroah.com>

>> Greg, Would you mind picking this patch series through your char-misc tree?
> 
> I'm sorry, but this person is in my blacklist

Some developers know this communication setting in the meantime.


> and I don't have any of their emails, so I don't have these patches anywhere.

I find this kind of feedback inappropriate.

You chose to exclude my update suggestions at a specific point in time.
They are still publicly available as they were stored also by other
information systems despite my messages vanish from your personal mail in-box
for a while.


> If you wish to have them applied, please resend them with your acked-by,

I am curious how other contributors will think about the shown change patterns.


> or just ignore them, it's up to you.

This reaction is also a possible option depending on your development priorities
for the affected software modules.

I hope that remaining open issues can be improved as desired after a bit of
constructive software development discussion.

Regards,
Markus

      reply	other threads:[~2017-05-15  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  8:54 [PATCH 0/2] Industry-pack bus: Adjustments for two function implementations SF Markus Elfring
2017-05-13  8:55 ` [PATCH 1/2] ipack: Delete an error message for a failed memory allocation in ipack_device_read_id() SF Markus Elfring
2017-05-15  9:08   ` Samuel Iglesias Gonsálvez
2017-05-15  9:08     ` [PATCH 2/2] ipack: Improve a size determination in ipack_bus_register() Samuel Iglesias Gonsálvez
2017-05-13  8:56 ` SF Markus Elfring
2017-05-15  4:52   ` Samuel Iglesias Gonsálvez
2017-05-15  5:56     ` Greg Kroah-Hartman
2017-05-15  6:40       ` 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=161221bf-26a7-6f45-6e2e-b166654aaee8@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=industrypack-devel@lists.sourceforge.net \
    --cc=jens.taprogge@taprogge.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=siglesias@igalia.com \
    /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