All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
Cc: devel@driverdev.osuosl.org, forest@alittletooquiet.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi
Date: Fri, 19 Nov 2021 15:17:49 +0100	[thread overview]
Message-ID: <YZeyDSa6ujv6rPMT@kroah.com> (raw)
In-Reply-To: <20211119133644.GB2519@alb3rt0-VirtualBox>

On Fri, Nov 19, 2021 at 02:36:44PM +0100, Alberto Merciai wrote:
> driver-core$ ./scripts/get_maintainer.pl drivers/staging/vt6655/device.h
> Forest Bond <forest@alittletooquiet.net> (odd fixer:STAGING - VIA VT665X DRIVERS)
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM)
> Alberto Merciai <alb3rt0.m3rciai@gmail.com> (commit_signer:2/2=100%,authored:2/2=100%,added_lines:2/2=100%,removed_lines:2/2=100%)
> devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)

What kernel version is that?

The driverdev mailing list is very old and should not be used anymore.

Please always work against the latest version of the kernel, and for
development stuff, linux-next is usually best so you do not duplicate
any work that anyone else has done.

thanks,

greg k-h

  reply	other threads:[~2021-11-19 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 20:27 [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi Alberto Merciai
2021-11-19  6:38 ` Greg KH
2021-11-19 13:36   ` Alberto Merciai
2021-11-19 14:17     ` Greg KH [this message]
2021-11-19  8:51 ` Dan Carpenter
2021-11-19 12:23   ` Alberto Merciai
2021-11-19 12:29     ` Greg KH
2021-11-19 18:51       ` Your Name

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=YZeyDSa6ujv6rPMT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alb3rt0.m3rciai@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=forest@alittletooquiet.net \
    --cc=linux-kernel@vger.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 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.