From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tharunkumar.Pasumarthi@microchip.com
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa@kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH i2c-master] i2c: microchip: pci1xxxx: Update Timing registers
Date: Mon, 20 Mar 2023 14:37:26 +0200 [thread overview]
Message-ID: <ZBhThvAm8yAEbNtS@smile.fi.intel.com> (raw)
In-Reply-To: <PH7PR11MB5958DE8BDC2B824B4961379A9B839@PH7PR11MB5958.namprd11.prod.outlook.com>
On Sun, Mar 19, 2023 at 02:42:37PM +0000, Tharunkumar.Pasumarthi@microchip.com wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Thursday, March 16, 2023 4:45 PM
> > To: Tharunkumar Pasumarthi - I67821
> > <Tharunkumar.Pasumarthi@microchip.com>
> >
> > On Thu, Mar 16, 2023 at 09:02:23AM +0530, Tharun Kumar P wrote:
> > > Update I2C timing registers based on latest hardware design.
> >
> > What about older designs?
>
> Older design is updated due to a bug. No future changes are expected in the timing registers going forward.
Do you have customers for the older designs in the wild?
P.S> All this has to be mentioned in the commit message to assure maintainers
that you are not going to break things for the existing users.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-03-20 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:32 [PATCH i2c-master] i2c: microchip: pci1xxxx: Update Timing registers Tharun Kumar P
2023-03-16 11:14 ` Andy Shevchenko
2023-03-19 14:42 ` Tharunkumar.Pasumarthi
2023-03-20 12:37 ` Andy Shevchenko [this message]
2023-03-20 12:51 ` Tharunkumar.Pasumarthi
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=ZBhThvAm8yAEbNtS@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Tharunkumar.Pasumarthi@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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