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>,
	linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Eugene Korenevsky" <ekorenevsky@gmail.com>,
	"Günter Röck" <linux@roeck-us.net>,
	"Jaejoong Kim" <climbbb.kim@gmail.com>,
	"Johan Hovold" <johan@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Mathias Nyman" <mathias.nyman@linux.intel.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: USB: core: Improve unlocking of a mutex in two functions
Date: Sun, 05 Nov 2017 09:33:15 +0000	[thread overview]
Message-ID: <73765f7c-57b6-9ade-bca3-4d65b30f2d5d@users.sourceforge.net> (raw)
In-Reply-To: <20171105073013.GA1431@kroah.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1504 bytes --]

> Don't worry, or waste your time, I don't take patches from this author
> as they are in my blacklist.

I am curious if our dialogue can become more constructive again. 🌈


I can offer another bit of information for this software development discussion. 💭

The affected source files can be compiled for the processor architecture “x86_64”
by a tool like “GCC 6.4.1+r251631-1.3” from the software distribution
“openSUSE Tumbleweed” with the following command example.

my_cc=/usr/bin/gcc-6 \
&& my_module1=drivers/usb/core/hub.o \
&& my_module2=drivers/usb/core/message.o \
&& git checkout next-20171102 \
&& make -j4 CC="${my_cc}" HOSTCC="${my_cc}" allmodconfig "${my_module1}" "${my_module2}" \
&& size "${my_module1}" "${my_module2}" \
&& git checkout ':/^USB: core: Improve unlocking of a mutex in two functions' \
&& make -j4 CC="${my_cc}" HOSTCC="${my_cc}" allmodconfig "${my_module1}" "${my_module2}" \
&& size "${my_module1}" "${my_module2}"


🔮 Do you find the following differences useful for further clarification?

╔═════════╤══════╗
║ module  │ text ║
╠═════════╪══════╣
║ hub     │ -16  ║
║ message │ -48  ║
╚═════════╧══════╝


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-11-05  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 20:12 [PATCH] USB: core: Improve unlocking of a mutex in two functions SF Markus Elfring
2017-11-04 23:25 ` Geert Uytterhoeven
2017-11-05  7:30   ` Greg Kroah-Hartman
2017-11-05  9:33     ` SF Markus Elfring [this message]
2017-11-05  8:29   ` SF Markus Elfring

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=73765f7c-57b6-9ade-bca3-4d65b30f2d5d@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=climbbb.kim@gmail.com \
    --cc=corbet@lwn.net \
    --cc=ekorenevsky@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mathias.nyman@linux.intel.com \
    --cc=mchehab@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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