public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: Tony Olech <tony.olech@elandigitalsystems.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mmc: vub300: Use common code in __download_offload_pseudocode()
Date: Tue, 31 Oct 2017 09:15:38 +0000	[thread overview]
Message-ID: <b809399c-6bd0-5a39-d2b9-442f7d008e72@users.sourceforge.net> (raw)
In-Reply-To: <20171031084552.mvvn73pfew4rebsd@mwanda>

>>> What's the advantage of this patch?  The new code seems more complicated
>>> to me and GCC automatically reuses duplicate constant strings so there
>>> is no memory savings.
>>
>> It looked to me that the error path got a bit cleaner. However, I
>> guess it's matter of taste.
>>
>> If you insist, I can drop it.
> 
> I'm on the kernel-janitors list so I am CC'd on all of Markus's patches.

Do you want that I omit this address from the list of recipients?


> It's not my code and I'm tired of being the anti-Markus guy

Interesting …

But I got the impression that this special relationship resulted
also in a few useful side effects.


> so this patch is fine.

Thanks for another bit of acceptance.


> Markus has a tool that finds duplicate strings and he uses gotos
> to avoid them.

Yes. - The script which I am using for the semantic patch language
(Coccinelle software) can not only find this implementation detail
but also duplicate source code generally to some degree.


> I don't think duplicate strings are a problem

They can become an issue for further considerations if inappropriate
error messages were used for example.

There are more statement combinations which can be improved a bit more.


> or that it's a good idea to send over a hundred patches using this method.

The change acceptance is varying as usual.


> But many people have explained that to Markus already

I hope that my contributions can improve the affected software in some areas.


> and that's not the bigger picture which is about error handling and labels.
> What I like are labels that are necessary and self explanatory.

It seems that this is a topic where you got strong opinions about.


> You're reading along and you're like "what happens at the err" label?

Would you accept any further adjustments around questionable jump targets?

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  9:15 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 [this message]
2017-10-31 15:10         ` Ulf Hansson
2017-10-31 15:42           ` 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=b809399c-6bd0-5a39-d2b9-442f7d008e72@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