From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: giometti@enneenne.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] pps: generators: tio: fix platform_set_drvdata()
Date: Mon, 17 Mar 2025 09:26:59 +0200 [thread overview]
Message-ID: <Z9fOw6iu37GVxD48@smile.fi.intel.com> (raw)
In-Reply-To: <20250315133140.1707949-1-raag.jadav@intel.com>
On Sat, Mar 15, 2025 at 07:01:40PM +0530, Raag Jadav wrote:
> Set driver_data correctly and fix illegal memory access on driver reload.
Do you have it in practice or you are thinking it will be like this?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-17 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 13:31 [PATCH v1] pps: generators: tio: fix platform_set_drvdata() Raag Jadav
2025-03-16 15:24 ` Rodolfo Giometti
2025-03-17 7:26 ` Andy Shevchenko [this message]
2025-03-17 7:40 ` Raag Jadav
2025-03-17 7:47 ` Andy Shevchenko
2025-03-17 7:32 ` Greg KH
2025-03-17 7:43 ` Raag Jadav
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=Z9fOw6iu37GVxD48@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=giometti@enneenne.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raag.jadav@intel.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