public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>, forest@forestbond.com
Cc: Dorine Tipo <dorine.a.tipo@gmail.com>,
	gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	outreachy@lists.linux.dev
Subject: Re: [PATCH v3] staging: vt6655: Remove unused function RFbAL7230SelectChannelPostProcess
Date: Thu, 14 Mar 2024 19:45:28 +0100	[thread overview]
Message-ID: <66b9d80f-94f2-44f5-8ad9-b73caa14bb44@gmail.com> (raw)
In-Reply-To: <4e162fac-078e-4a37-9a6a-fad186b0d27a@moroto.mountain>

On 3/14/24 07:36, Dan Carpenter wrote:
> On Thu, Mar 14, 2024 at 06:33:58AM +0100, Philipp Hortmann wrote:
>> On 3/11/24 08:31, Dan Carpenter wrote:
>>> The main issue with this patch is that it doesn't apply, but I have a
>>> few other comments as well.
>>>
>>> Why is Forest Bond not on the CC list?  Please use get_maintainer.pl.
>>
>> Hi Dan,
>>
>> reason why some omit Forest Bond is that the emailaddress seems to not exist
>> anymore - find below. Can I issue a patch to change this?
>>
>> Who is then entered to the M: in MAINTAINERS?
>> STAGING - VIA VT665X DRIVERS
>> M:	Forest Bond <forest@alittletooquiet.net>
>> S:	Odd Fixes
>> F:	drivers/staging/vt665?/
>>
> 
> Yeah.  His current email is forest@forestbond.com, but let's mark it as
> orphan.  You actually have this hardware, don't you?  Do you want to
> take over?
> 
> regards,
> dan carpenter
> 

Hi Dan,

I do have vt6655 and vt6656 hardware.
But I have no idea what commitment I am entering into.
Please send me a link to a description of what my obligations are?

Thanks for your support.

Bye Philipp

  reply	other threads:[~2024-03-14 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  1:56 [PATCH] staging: vt6655: Remove unused function from rf.h RFbAL7230SelectChannelPostProcess Dorine Tipo
2024-03-11  3:56 ` [PATCH v2] staging: vt6655: Remove unused function RFbAL7230SelectChannelPostProcess Dorine Tipo
2024-03-11  5:46   ` Dan Carpenter
2024-03-11  6:07   ` [PATCH v3] " Dorine Tipo
2024-03-11  7:31     ` Dan Carpenter
2024-03-14  5:33       ` Philipp Hortmann
2024-03-14  6:36         ` Dan Carpenter
2024-03-14 18:45           ` Philipp Hortmann [this message]
2024-03-15  5:00             ` Bagas Sanjaya
2024-03-16 13:33               ` Philipp Hortmann
2024-03-16 16:10                 ` Dan Carpenter

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=66b9d80f-94f2-44f5-8ad9-b73caa14bb44@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dorine.a.tipo@gmail.com \
    --cc=forest@forestbond.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy@lists.linux.dev \
    /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