All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: "Shenhar, Talel" <talel@amazon.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-pm@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] thermal: mmio: remove some dead code
Date: Mon, 03 Jun 2019 10:51:01 +0000	[thread overview]
Message-ID: <20190603105101.GH31203@kadam> (raw)
In-Reply-To: <20190603020901.GA7918@localhost.localdomain>

On Sun, Jun 02, 2019 at 07:09:03PM -0700, Eduardo Valentin wrote:
> hey Dan, Talel,
> 
> On Mon, May 20, 2019 at 05:26:51PM +0300, Shenhar, Talel wrote:
> > 
> > On 5/15/2019 12:34 PM, Dan Carpenter wrote:
> > >The platform_get_resource() function doesn't return error pointers, it
> > >returns NULL.  The way this is normally done, is that we pass the NULL
> > >resource to devm_ioremap_resource() and then check for errors from that.
> > >See the comment in front of devm_ioremap_resource() for more details.
> > >
> > >Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Acked-by: Talel Shenhar <talel@amazon.com>
> 
> Cool. I will be collecting this. The only change I will do while
> applying this is that the subject will look like this:
> "thermal: thermal_mmio: remove some dead code"
> 
> Just to match the file / driver name.
> 

I feel like it's duplicative to have "thermal" twice, but whatever.
What I normally do is I copy-and-paste what other people use because the
prefered format varies from subsystem to subsystem.  Here the only
previous patch was:

71aa3693493d thermal: Introduce Amazon's Annapurna Labs Thermal Driver

This format was obviously even worse...

I'm often the first person to send a patch for new drivers.  It used to
be common for people to not use a correct patch prefix for the patch
which adds a driver.  But what happened was people got annoyed with the
prefixes I chose.  And I was like, "Nah.  Forget about it.  I got here
first and I claim this land for my ownself.  Be grateful I didn't choose
a snide or rude patch prefix because that's my authority as a prefix
chooser."

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: "Shenhar, Talel" <talel@amazon.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	linux-pm@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] thermal: mmio: remove some dead code
Date: Mon, 3 Jun 2019 13:51:01 +0300	[thread overview]
Message-ID: <20190603105101.GH31203@kadam> (raw)
In-Reply-To: <20190603020901.GA7918@localhost.localdomain>

On Sun, Jun 02, 2019 at 07:09:03PM -0700, Eduardo Valentin wrote:
> hey Dan, Talel,
> 
> On Mon, May 20, 2019 at 05:26:51PM +0300, Shenhar, Talel wrote:
> > 
> > On 5/15/2019 12:34 PM, Dan Carpenter wrote:
> > >The platform_get_resource() function doesn't return error pointers, it
> > >returns NULL.  The way this is normally done, is that we pass the NULL
> > >resource to devm_ioremap_resource() and then check for errors from that.
> > >See the comment in front of devm_ioremap_resource() for more details.
> > >
> > >Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Acked-by: Talel Shenhar <talel@amazon.com>
> 
> Cool. I will be collecting this. The only change I will do while
> applying this is that the subject will look like this:
> "thermal: thermal_mmio: remove some dead code"
> 
> Just to match the file / driver name.
> 

I feel like it's duplicative to have "thermal" twice, but whatever.
What I normally do is I copy-and-paste what other people use because the
prefered format varies from subsystem to subsystem.  Here the only
previous patch was:

71aa3693493d thermal: Introduce Amazon's Annapurna Labs Thermal Driver

This format was obviously even worse...

I'm often the first person to send a patch for new drivers.  It used to
be common for people to not use a correct patch prefix for the patch
which adds a driver.  But what happened was people got annoyed with the
prefixes I chose.  And I was like, "Nah.  Forget about it.  I got here
first and I claim this land for my ownself.  Be grateful I didn't choose
a snide or rude patch prefix because that's my authority as a prefix
chooser."

regards,
dan carpenter


  reply	other threads:[~2019-06-03 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  9:34 [PATCH] thermal: mmio: remove some dead code Dan Carpenter
2019-05-15  9:34 ` Dan Carpenter
2019-05-20 14:26 ` Shenhar, Talel
2019-05-20 14:26   ` Shenhar, Talel
2019-06-03  2:09   ` Eduardo Valentin
2019-06-03  2:09     ` Eduardo Valentin
2019-06-03 10:51     ` Dan Carpenter [this message]
2019-06-03 10:51       ` Dan Carpenter

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=20190603105101.GH31203@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=talel@amazon.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 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.