mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: linux-kernel@vger.kernel.org, mcgrof@kernel.org
Subject: Re: [PATCH] firmware: raspberrypi: Eliminate use of time_to_tm
Date: Tue, 7 Nov 2017 20:43:01 +0100	[thread overview]
Message-ID: <20171107194301.GC22894@wotan.suse.de> (raw)
In-Reply-To: <1509832306-1104-1-git-send-email-himanshujha199640@gmail.com>

On Sun, Nov 05, 2017 at 03:21:46AM +0530, Himanshu Jha wrote:
> time_to_tm function is deprecated due to y2038 problem, therefore use
> time64_to_tm instead.

Use ./scripts/get_maintainer.pl foo.patch and resend with the
respective folks addressed to as needed (To or Cc as indicated
by the script).

Your commit log should reference why *time_to_tm()* is now
deprecated in favor for time64_to_tm() to make maintainer's
lives easier so that their lookup is faster.

Resend with these details. Likewise for the other patches for
which you failed to do any of this for.

  Luis

> Signed-off-by: Himanshu Jha <himanshujha199640@gmail.com>
> ---
>  drivers/firmware/raspberrypi.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/firmware/raspberrypi.c b/drivers/firmware/raspberrypi.c
> index dd506cd..aa4c797 100644
> --- a/drivers/firmware/raspberrypi.c
> +++ b/drivers/firmware/raspberrypi.c
> @@ -166,7 +166,7 @@ EXPORT_SYMBOL_GPL(rpi_firmware_property);
>  static void
>  rpi_firmware_print_firmware_revision(struct rpi_firmware *fw)
>  {
> -	u32 packet;
> +	time64_t packet;
>  	int ret = rpi_firmware_property(fw,
>  					RPI_FIRMWARE_GET_FIRMWARE_REVISION,
>  					&packet, sizeof(packet));
> @@ -174,7 +174,7 @@ rpi_firmware_print_firmware_revision(struct rpi_firmware *fw)
>  	if (ret == 0) {
>  		struct tm tm;
>  
> -		time_to_tm(packet, 0, &tm);
> +		time64_to_tm(packet, 0, &tm);
>  
>  		dev_info(fw->cl.dev,
>  			 "Attached to firmware from %04ld-%02d-%02d %02d:%02d\n",
> -- 
> 2.7.4
> 
> 

-- 
Luis Rodriguez, SUSE LINUX GmbH
Maxfeldstrasse 5; D-90409 Nuernberg

      reply	other threads:[~2017-11-07 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 21:51 Himanshu Jha
2017-11-07 19:43 ` Luis R. Rodriguez [this message]

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=20171107194301.GC22894@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=himanshujha199640@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®