linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: 唐彬 <tangbin@cmss.chinamobile.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: hwrng: omap - Delete an error message in of_get_omap_rng_device_details()
Date: Sat, 4 Apr 2020 18:49:22 +0200	[thread overview]
Message-ID: <e71d56f1-6fce-5e2d-9719-1385ef3b0811@web.de> (raw)
In-Reply-To: <2020040423261552036811@cmss.chinamobile.com>

> I don't know why you always cc me in your patch
> which is similar type  I have submitted。

I noticed your selection of possible changes (and corresponding patch reviews).

* Thus I assumed that you are interested in further software evolution
  to some degree in such a design direction.
  Do you want that I omit your mail address from my patches?

* I picked also a few of your change ideas up for their application
  together with development tools I am familiar with.


> Let me study

I hope so.


> to thank you ?

This possibility can also be occasionally nice.


> You are a senior,

Such a view might be appropriate.


> I have thanked you for your instruction,

I hope that our collaboration will evolve further in constructive ways.


> and I have understand what your question:

Would we like to achieve a better common understanding?


> How do you think about to change any more source files in a systematic way?

Advanced source code analysis can point several update candidates out.
An execution of a script for the semantic patch language (Coccinelle software)
indicates change possibilities around calls of the function “platform_get_irq”
in 74 source files of the software “Linux next-20200402” at the moment.
Source code search patterns can be extended after some clarification.

Regards,
Markus

  parent reply	other threads:[~2020-04-04 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 14:56 [PATCH] hwrng: omap - Delete an error message in of_get_omap_rng_device_details() Markus Elfring
     [not found] ` <2020040423261552036811@cmss.chinamobile.com>
2020-04-04 16:49   ` Markus Elfring [this message]
     [not found]     ` <2020040505380926003012@cmss.chinamobile.com>
2020-04-05  5:44       ` Clarification for software development opportunities Markus Elfring
2020-04-06  6:54       ` hwrng: omap - Delete an error message in of_get_omap_rng_device_details() Markus Elfring
2020-04-16  6:51 ` [PATCH] " Herbert Xu

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=e71d56f1-6fce-5e2d-9719-1385ef3b0811@web.de \
    --to=markus.elfring@web.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tangbin@cmss.chinamobile.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;
as well as URLs for NNTP newsgroup(s).