All of lore.kernel.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Joe Perches <joe@perches.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: Input-gameport: Replace some printk() calls by pr_info() in joydump_connect()
Date: Sat, 24 Sep 2016 17:20:48 +0000	[thread overview]
Message-ID: <69699b11-88fb-93ea-24a2-9ff697b5f439@users.sourceforge.net> (raw)
In-Reply-To: <20160924163912.GA40187@dtor-ws>

> The desired output should not be broken in conversion, which you did.

I dared to change another source code place a bit too much perhaps.


> Do you know how syslog works and why the transformation is not correct.

I imagine that there are chances to improve the software situation a bit more,
aren't there?


> I am also curious as to why you are patching joydump?

The discussed function implementation contains update candidates.

One of them was detected by the execution of a script for the semantic patch
language (Coccinelle software).
I identified further update possibilities after the opportunity for using
the function "kmalloc_array" also in this software module.


> Are you working on extending it?

I attempted just another software refactoring.

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Joe Perches <joe@perches.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: Input-gameport: Replace some printk() calls by pr_info() in joydump_connect()
Date: Sat, 24 Sep 2016 19:20:48 +0200	[thread overview]
Message-ID: <69699b11-88fb-93ea-24a2-9ff697b5f439@users.sourceforge.net> (raw)
In-Reply-To: <20160924163912.GA40187@dtor-ws>

> The desired output should not be broken in conversion, which you did.

I dared to change another source code place a bit too much perhaps.


> Do you know how syslog works and why the transformation is not correct.

I imagine that there are chances to improve the software situation a bit more,
aren't there?


> I am also curious as to why you are patching joydump?

The discussed function implementation contains update candidates.

One of them was detected by the execution of a script for the semantic patch
language (Coccinelle software).
I identified further update possibilities after the opportunity for using
the function "kmalloc_array" also in this software module.


> Are you working on extending it?

I attempted just another software refactoring.

Regards,
Markus

  reply	other threads:[~2016-09-24 17:20 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-24 13:45 [PATCH 0/4] Input-gameport: Fine-tuning for joydump_connect() SF Markus Elfring
2016-09-24 13:45 ` SF Markus Elfring
2016-09-24 13:46 ` [PATCH 1/4] Input-gameport: Use kmalloc_array() in joydump_connect() SF Markus Elfring
2016-09-24 13:46   ` SF Markus Elfring
2016-09-24 16:42   ` Dmitry Torokhov
2016-09-24 16:42     ` Dmitry Torokhov
2016-09-24 17:04     ` SF Markus Elfring
2016-09-24 17:04       ` SF Markus Elfring
2016-09-24 13:47 ` [PATCH 2/4] Input-gameport: Delete an error message for a failed memory allocation SF Markus Elfring
2016-09-24 13:47   ` SF Markus Elfring
2016-09-24 13:48 ` [PATCH 3/4] Input-gameport: Add the macro "pr_fmt" for module "joydump" SF Markus Elfring
2016-09-24 13:48   ` SF Markus Elfring
2016-09-24 16:41   ` Dmitry Torokhov
2016-09-24 16:41     ` Dmitry Torokhov
2016-09-24 16:55     ` SF Markus Elfring
2016-09-24 16:55       ` SF Markus Elfring
2016-09-24 17:03       ` Joe Perches
2016-09-24 17:03         ` Joe Perches
2016-09-24 17:45         ` SF Markus Elfring
2016-09-24 17:45           ` SF Markus Elfring
2016-09-24 18:01           ` Joe Perches
2016-09-24 18:01             ` Joe Perches
2016-09-24 18:45             ` SF Markus Elfring
2016-09-24 18:45               ` SF Markus Elfring
2016-09-24 13:50 ` [PATCH 4/4] Input-gameport: Replace some printk() calls by pr_info() in joydump_connect() SF Markus Elfring
2016-09-24 13:50   ` SF Markus Elfring
2016-09-24 16:13   ` Joe Perches
2016-09-24 16:13     ` Joe Perches
2016-09-24 16:32     ` SF Markus Elfring
2016-09-24 16:32       ` SF Markus Elfring
2016-09-24 16:39       ` Dmitry Torokhov
2016-09-24 16:39         ` Dmitry Torokhov
2016-09-24 17:20         ` SF Markus Elfring [this message]
2016-09-24 17:20           ` SF Markus Elfring
2016-09-24 16:47       ` [PATCH 4/4] " Joe Perches
2016-09-24 16:47         ` Joe Perches
2016-09-24 19:50         ` SF Markus Elfring
2016-09-24 19:50           ` SF Markus Elfring
2016-09-24 16:41     ` [PATCH 4/4] " SF Markus Elfring
2016-09-24 16:41       ` SF Markus Elfring
2016-09-25  7:15     ` [PATCH v2 3/3] " SF Markus Elfring
2016-09-25  7:15       ` SF Markus Elfring
2016-09-25  7:31       ` Joe Perches
2016-09-25  7:31         ` Joe Perches
2016-09-25  7:45         ` SF Markus Elfring
2016-09-25  7:45           ` 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=69699b11-88fb-93ea-24a2-9ff697b5f439@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=joe@perches.com \
    --cc=julia.lawall@lip6.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.