public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <william.gray@linaro.org>
To: Paul Demetrotion <pdemetrotion@winsystems.com>,
	techsupport@winsystems.com
Cc: Guenter Roeck <linux@roeck-us.net>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] watchdog: ebc-c384_wdt: Migrate to the regmap API
Date: Sun, 2 Apr 2023 10:07:36 -0400	[thread overview]
Message-ID: <ZCmMKC+/RwmWshCP@fedora> (raw)
In-Reply-To: <87df4524-5a64-c285-238d-ac1ae0c31249@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Tue, Mar 14, 2023 at 10:47:28AM -0700, Guenter Roeck wrote:
> On 3/14/23 08:29, William Breathitt Gray wrote:
> > The regmap API supports IO port accessors so we can take advantage of
> > regmap abstractions rather than handling access to the device registers
> > directly in the driver.
> > 
> > Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
> 
> The changes are too invasive to accept without testing.
> I hope we can get a Tested-by: tag from someone. Other than
> that, we are good to go from my perspective.
> 
> Thanks,
> Guenter

Paul,

Is anyone at WINSYSTEMS interested in this driver? I no longer have
access to this hardware so I can no longer maintain this driver, and the
original users of this driver indicated to me that they have moved on to
another device. If there is no longer interest at WINSYSTEMS to maintain
this driver, perhaps we should discuss removal of it from the Linux
codebase.

William Breathitt Gray

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-04-02 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 15:29 [PATCH v2] watchdog: ebc-c384_wdt: Migrate to the regmap API William Breathitt Gray
2023-03-14 15:50 ` Andy Shevchenko
2023-03-14 16:14   ` Guenter Roeck
2023-03-14 16:31   ` William Breathitt Gray
2023-03-14 16:42     ` Guenter Roeck
2023-03-14 17:47 ` Guenter Roeck
2023-04-02 14:07   ` William Breathitt Gray [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=ZCmMKC+/RwmWshCP@fedora \
    --to=william.gray@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pdemetrotion@winsystems.com \
    --cc=techsupport@winsystems.com \
    --cc=wim@linux-watchdog.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