[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YyQn6+C7kkQ7u5qi@kadam>
Date: Fri, 16 Sep 2022 10:38:19 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Nam Cao <namcaov@...il.com>
Cc: Philipp Hortmann <philipp.g.hortmann@...il.com>,
forest@...ttletooquiet.net, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [RFC PATCH 0/5] staging: vt6655: Implement allocation failure
handling
On Fri, Sep 16, 2022 at 09:11:58AM +0200, Nam Cao wrote:
> > Find in this email a comment from Greg about RFC:
> > https://lore.kernel.org/linux-gpio/YwS4WDekXM3UQ7Yo@kroah.com/
> > This patch is marked as "RFC" but I don't see any questions that you
> > have here. Please resolve anything you think needs to be handled and
> > submit a "this series is ok to be merged" version.
> >
> > May be this is applicable to this patch as well.
>
> I add the RFC tag to "tells maintainers should review your patch thoroughly,
> and provide feedback. RFC is typically used when sending feature patches for
> the first time, or anytime the patch is more than just a simple bug fix."
> (from https://kernelnewbies.org/PatchTipsAndTricks). I was not aware that this
> tag may be interpreted differently. I can send a new patchset if necessary.
Clean up patches are much simpler than bug fixes. No need for an RFC.
But this patch does too many things and Greg will not apply it.
regards,
dan carpenter
Powered by blists - more mailing lists