public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Manuel Lauss <manuel.lauss@gmail.com>, linux-mips@linux-mips.org
Cc: "Paul Burton" <paul.burton@imgtec.com>,
	"Ralf Bächle" <ralf@linux-mips.org>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe()
Date: Thu, 25 May 2017 06:54:48 +0000	[thread overview]
Message-ID: <70394897-a67a-2b49-2d46-a20fb2de51f2@users.sourceforge.net> (raw)
In-Reply-To: <CAOLZvyH-DF_r77kzcVcn+A-tTov+aNZ1oGNQLnGWXE35UODqtQ@mail.gmail.com>

>> How do you think about to achieve a small code reduction also for this software module?
> 
> Generally speaking, sure.

Thanks for your interest in such a direction.


> But why remove just this one?  Is it because it loosely follows a
> pattern that was deemed removable in that slidedeck you linked to?

I derived another source code search approach from the implementation
of the check “OOM_MESSAGE” in the script “checkpatch.pl” for
the semantic patch language (Coccinelle software).
The involved search patterns are still evolving and the used lists
(or regular expressions) for function names where it might make sense
to reconsider the usage of special logging calls is therefore incomplete.


> (the "usb_submit_urb()" part)?

Would you like to extend the function selection for further considerations?


>> Do you find information from a Linux allocation failure report sufficient
>> for such a function implementation?
> 
> Yes, I wrote that code, and in case this driver doesn't load, I'd like
> to know precisely where initialization failed.
> I can happily spare a few bytes for that.

Does this kind of answer contain a bit of contradiction?

* Why do you seem to insist on another message if information from a Linux
  allocation failure report would be sufficient already also for this
  software module?

* Do you want that it can become easier to map a position in a backtrace
  to a place in your source code?

Regards,
Markus

  reply	other threads:[~2017-05-25  6:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 16:42 [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() SF Markus Elfring
2017-05-24 17:42 ` [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_pro Manuel Lauss
2017-05-24 18:15   ` SF Markus Elfring
2017-05-24 18:26     ` Randy Dunlap
2017-05-24 20:26       ` MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() SF Markus Elfring
2017-05-25  6:20     ` [PATCH] MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_pro Manuel Lauss
2017-05-25  6:54       ` SF Markus Elfring [this message]
2017-05-25  9:29         ` MIPS: Alchemy: Delete an error message for a failed memory allocation in alchemy_pci_probe() Manuel Lauss
2017-05-25 10:57           ` 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=70394897-a67a-2b49-2d46-a20fb2de51f2@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@gmail.com \
    --cc=paul.burton@imgtec.com \
    --cc=ralf@linux-mips.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