From: Stefano Brivio <sbrivio@redhat.com>
To: Veera <vkor@vkten.in>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] staging: sm750fb: makefile variable longline fix
Date: Thu, 12 Mar 2020 11:42:48 +0100 [thread overview]
Message-ID: <20200312114248.547750ef@elisabeth> (raw)
In-Reply-To: <20200312011444.GA1928@localhost>
On Thu, 12 Mar 2020 06:44:46 +0530
Veera <vkor@vkten.in> wrote:
> On Wed, Mar 11, 2020 at 05:58:39PM +0100, Stefano Brivio wrote:
> >
> > On Wed, 11 Mar 2020 18:41:02 +0530
> > R Veera Kumar <vkor@vkten.in> wrote:
> >
> > > -sm750fb-objs := sm750.o sm750_hw.o sm750_accel.o sm750_cursor.o ddk750_chip.o ddk750_power.o ddk750_mode.o
> > > -sm750fb-objs += ddk750_display.o ddk750_swi2c.o ddk750_sii164.o ddk750_dvi.o ddk750_hwi2c.o
> > > +sm750fb-objs := sm750.o sm750_hw.o sm750_accel.o sm750_cursor.o
> > > +sm750fb-objs += ddk750_chip.o ddk750_power.o ddk750_mode.o
> > > +sm750fb-objs += ddk750_display.o ddk750_swi2c.o ddk750_sii164.o
> > > +sm750fb-objs += ddk750_dvi.o ddk750_hwi2c.o
> >
> > ...and while this fixes the long lines for sure, a more common way is
> > to use backslashes at the end of the lines. Compare it with other
> > similar cases: you don't need to do something like:
> > drivers/staging/wfx/Makefile
> >
> > but what's done for example in:
> > drivers/staging/comedi/Makefile
> >
>
> Yes. I knew it. But thought preserving maintainer style may be right.
As a general rule, absolutely, but I wonder if we can even define a
"style" here at all. It's also the single occurrence of this, in this
file, and for this driver altogether.
--
Stefano
prev parent reply other threads:[~2020-03-12 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 13:11 [PATCH] staging: sm750fb: makefile variable longline fix R Veera Kumar
2020-03-11 16:58 ` [Outreachy kernel] " Stefano Brivio
2020-03-12 1:14 ` Veera
2020-03-12 10:42 ` Stefano Brivio [this message]
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=20200312114248.547750ef@elisabeth \
--to=sbrivio@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=vkor@vkten.in \
/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.