From: William Breathitt Gray <william.gray@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
Paul Demetrotion <pdemetrotion@winsystems.com>,
techsupport@winsystems.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Fred Eckert <Frede@cmslaser.com>
Subject: Re: [PATCH] watchdog: ebc-c384_wdt: Remove support
Date: Mon, 10 Apr 2023 10:51:42 -0400 [thread overview]
Message-ID: <ZDQifl7EB33dh/eu@fedora> (raw)
In-Reply-To: <7b0fbd06-73d0-7fa9-3f03-e788f1df4631@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Mon, Apr 10, 2023 at 07:43:37AM -0700, Guenter Roeck wrote:
> On 4/10/23 07:31, William Breathitt Gray wrote:
> > The current maintainer no longer has access to the device for testing,
> > the original user of this driver indicates that they have moved on to
> > another device, and the manufacturer WINSYSTEMS does not appear
> > interested in taking over support for this code.
> >
> > Signed-off-by: William Breathitt Gray <william.gray@linaro.org>
>
> A bit harsh, maybe. Just mark it as orphan for the time being.
>
> I see there are other Winsystems drivers. What are you going to do
> with those ?
>
> Guenter
Oops, I didn't mean for that commit message to sound so harsh but merely
log some brief reasons for the support removal for posterity. However, I
adjust this to orphan status rather than dropping; what is the process
to mark a driver as orphaned?
As for the other Winsystems drivers, I'm still able to test those so I
can continue maintainance of those -- although I'm always open if
WINSYSTEMS would like to join as a supporter, or a user co-maintainer
comes along. ;-)
William Breathitt Gray
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-10 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 14:31 [PATCH] watchdog: ebc-c384_wdt: Remove support William Breathitt Gray
2023-04-10 14:43 ` Guenter Roeck
2023-04-10 14:51 ` William Breathitt Gray [this message]
2023-04-10 15:01 ` Guenter Roeck
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=ZDQifl7EB33dh/eu@fedora \
--to=william.gray@linaro.org \
--cc=Frede@cmslaser.com \
--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 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.