From: nobuhiro1.iwamatsu@toshiba.co.jp (nobuhiro1.iwamatsu at toshiba.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 4.4.y-cip 05/10] rtc: pcf85363: Add support for NXP pcf85263 rtc
Date: Wed, 17 Jul 2019 23:20:29 +0000 [thread overview]
Message-ID: <OSAPR01MB3234A60856510B217AFE040992C90@OSAPR01MB3234.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OSBPR01MB2103ED72F24A325F68299855B8C90@OSBPR01MB2103.jpnprd01.prod.outlook.com>
Hi,
> -----Original Message-----
> From: Biju Das [mailto:biju.das at bp.renesas.com]
> Sent: Wednesday, July 17, 2019 4:16 PM
> To: iwamatsu nobuhiro(?? ?? ????????)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; cip-dev at lists.cip-project.org
> Subject: RE: [cip-dev] [PATCH 4.4.y-cip 05/10] rtc: pcf85363: Add support
> for NXP pcf85263 rtc
>
> Hi Nobuhiro,
>
> Thanks for the feedback.
>
> > Subject: RE: [cip-dev] [PATCH 4.4.y-cip 05/10] rtc: pcf85363: Add
> > support for NXP pcf85263 rtc
> >
> > Hi,
> >
> > > -----Original Message-----
> > > From: cip-dev-bounces at lists.cip-project.org
> > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Biju Das
> > > Sent: Tuesday, July 16, 2019 5:15 PM
> > > To: cip-dev at lists.cip-project.org
> > > Cc: Biju Das <biju.das@bp.renesas.com>
> > > Subject: [cip-dev] [PATCH 4.4.y-cip 05/10] rtc: pcf85363: Add
> > > support for NXP pcf85263 rtc
> > >
> > > commit fc979933bcf162595b6004d0de4effb64c323152 upstream.
> > >
> > > Add support for NXP pcf85263 real-time clock. pcf85263 rtc is
> > > compatible with pcf85363,except that pcf85363 has additional 64
> > > bytes of
> > RAM.
> > >
> > > 1 byte of nvmem is supported and exposed in sysfs (# is the instance
> > > number,starting with 0): /sys/bus/nvmem/devices/pcf85x63-#/nvmem
> > >
> > > Signed-off-by: Biju Das <biju.das@bp.renesas.com> [ Removed rtc
> > > nvmem support. Added I2C ID table for rtc-pcf85263 ]
> >
> > You've deleted Alexandre's Signed-off-by tag from original patch.
>
> Thanks for pointing this out. It is a mistake. Can you please fix this
> while applying to the tree?
>
> Or
>
> Do you want me to send another patch fixing this? Please let me know.
>
Pavel applied this patch with signed-off-by tag. Thanks Pavel.
Best regards,
Nobuhiro
next prev parent reply other threads:[~2019-07-17 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 8:15 [cip-dev] [PATCH 4.4.y-cip 00/10] Add RTC support Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 01/10] rtc: add support for NXP PCF85363 real-time clock Biju Das
2019-07-17 11:29 ` Pavel Machek
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 02/10] rtc: pcf85363: add .max_register in regmap_config Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 03/10] rtc: pcf85363: set time accurately Biju Das
2019-07-16 21:03 ` Pavel Machek
2019-07-17 7:47 ` Biju Das
2019-07-23 18:12 ` Ben Hutchings
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 04/10] dt-bindings: rtc: pcf85363: Document pcf85263 real-time clock Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 05/10] rtc: pcf85363: Add support for NXP pcf85263 rtc Biju Das
2019-07-17 7:08 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-17 7:16 ` Biju Das
2019-07-17 23:20 ` nobuhiro1.iwamatsu at toshiba.co.jp [this message]
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 06/10] ARM: dts: r8a77470: Add I2C4 support Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 07/10] ARM: dts: r8a77470: Add I2C[0123] support Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 08/10] ARM: shmobile: Enable NXP pcf85363 rtc in shmobile_defconfig Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 09/10] ARM: multi_v7_defconfig: Enable NXP pcf85363 rtc Biju Das
2019-07-16 8:15 ` [cip-dev] [PATCH 4.4.y-cip 10/10] ARM: dts: iwg23s-sbc: Enable RTC Biju Das
2019-07-17 11:45 ` [cip-dev] [PATCH 4.4.y-cip 00/10] Add RTC support Pavel Machek
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=OSAPR01MB3234A60856510B217AFE040992C90@OSAPR01MB3234.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=cip-dev@lists.cip-project.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.