From: Greg KH <gregkh@linuxfoundation.org>
To: Karolina Drobnik <karolinadrobnik@gmail.com>
Cc: Joe Perches <joe@perches.com>,
outreachy-kernel@googlegroups.com, forest@alittletooquiet.net,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6655: Fix line wrapping in rf.c file
Date: Tue, 19 Oct 2021 13:12:30 +0200 [thread overview]
Message-ID: <YW6oHsli56urDry6@kroah.com> (raw)
In-Reply-To: <810a4e29b0c54520a30cae4d37fde0a59ea3d83b.camel@gmail.com>
On Tue, Oct 19, 2021 at 11:59:56AM +0100, Karolina Drobnik wrote:
> Hi,
>
> Thank you very much for your comments.
>
> On Mon, 2021-10-18 at 17:12 +0200, Greg KH wrote:
> > Also, these are all just fine as-is for now. A better way to make
> > these lines smaller is to use better variable and function names
> > that are shorter and make sense :)
>
> I have v2 ready but I'm not sure, given the Joe's patch, if my solution
> is a satisfactory one. I didn't jump on such refactoring as I'm still
> learning about the codebase/process and didn't want to muddle the
> waters (...more than I do already).
>
> Greg, what would you prefer? Should I back up with my patch, pick
> something else and let Joe's patch be merged?
Joe hasn't submitted it in a format that I can take it in, so that is up
to you, I can't tell you want to work on :)
good luck!
greg k-h
next prev parent reply other threads:[~2021-10-19 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 15:05 [PATCH] staging: vt6655: Fix line wrapping in rf.c file Karolina Drobnik
2021-10-18 15:10 ` [Outreachy kernel] " Julia Lawall
2021-10-18 15:12 ` Greg KH
2021-10-19 5:56 ` Joe Perches
2021-10-19 10:59 ` Karolina Drobnik
2021-10-19 11:12 ` Greg KH [this message]
2021-10-19 12:26 ` Joe Perches
2021-10-19 13:12 ` [Outreachy kernel] " Fabio M. De Francesco
2021-10-19 13:07 ` Fabio M. De Francesco
2021-10-19 15:08 ` Karolina Drobnik
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=YW6oHsli56urDry6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=joe@perches.com \
--cc=karolinadrobnik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox