All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joel Becker <jlbec@evilplan.org>, Christoph Hellwig <hch@lst.de>,
	Kent Gibson <warthog618@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [GIT PULL] configfs-based GPIO simulator for v5.16
Date: Sun, 7 Nov 2021 13:36:27 +0100	[thread overview]
Message-ID: <YYfIS/sK+OAF8xsA@kroah.com> (raw)
In-Reply-To: <CACRpkdZchV1M+BYhMYoXNj_+uUHZeydW5-nHGTjD2bZedAqKKw@mail.gmail.com>

On Sun, Nov 07, 2021 at 01:16:58PM +0100, Linus Walleij wrote:
> On Thu, Nov 4, 2021 at 8:01 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> 
> > A couple months have passed with a few more iterations and I still can't get
> > any meaningful reviews from the configfs maintainers (nor NAKs for that
> > matter). I decided to give it another try and send it to you directly again.
> 
> I think this indicates that configfs is partly orphaned. If not formally
> then practically. Let's poke Greg and see what he says, configfs
> is important for USB.
> 
> I do understand the lack of maintainership hours and that people have
> more important things to do, we all suffer from this.
> 
> If you are the only one who really care maybe we should consider listing
> you as configfs (co-)maintainer as well?

configfs has two current maintainers, I don't think we need another one,
but they should have at least responded to the patch series previously
:(

greg k-h

  reply	other threads:[~2021-11-07 12:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 19:00 [GIT PULL] configfs-based GPIO simulator for v5.16 Bartosz Golaszewski
2021-11-07 12:16 ` Linus Walleij
2021-11-07 12:36   ` Greg KH [this message]
2021-11-08  7:44     ` Christoph Hellwig
2021-11-08  8:45       ` Bartosz Golaszewski
2021-11-08  7:45   ` Christoph Hellwig
2021-11-12 14:46 ` Bartosz Golaszewski

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=YYfIS/sK+OAF8xsA@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=hch@lst.de \
    --cc=jlbec@evilplan.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=warthog618@gmail.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 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.