From: Greg KH <gregkh@linuxfoundation.org>
To: Tanju Brunostar <tanjubrunostar0@gmail.com>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
outreachy@lists.linux.dev
Subject: Re: Request for assistance
Date: Thu, 20 Oct 2022 14:10:17 +0200 [thread overview]
Message-ID: <Y1E6qYkzkRxlloNp@kroah.com> (raw)
In-Reply-To: <CAHJEyKX=yyuyYFajs880CuPdc019dBOm_LCkgXHzjFaA-Jgt2A@mail.gmail.com>
On Thu, Oct 20, 2022 at 12:34:02PM +0100, Tanju Brunostar wrote:
> On Thu, Oct 20, 2022 at 12:27 PM Bhaskar Chowdhury
> <unixbhaskar@gmail.com> wrote:
> >
> > Use forward slash at the end every single chunk or piece of that line.
> >
> > Example :
> >
> > Veryyyyyyylooooooong. Linerrrrrrrrrrrrrrr
> >
> > Veryyyyyyyyyyyyy /
> >
> > Looooonggggggggg /
> >
> >
> > Linerrrrrrrrrrr /
No, please do not do that in normal C code. That's only for rare cases,
like in a #define, that this style would be needed.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-20 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 11:00 Request for assistance Ubuntu
2022-10-20 11:10 ` Greg KH
2022-10-20 11:14 ` Tanju Brunostar
2022-10-20 11:59 ` Julia Lawall
[not found] ` <CAOkYk0iU0B98JsH77avky--AS19V=GhQox2f_b4PAG3ZBB+SVQ@mail.gmail.com>
2022-10-20 11:34 ` Tanju Brunostar
2022-10-20 12:10 ` Greg KH [this message]
2022-10-20 14:39 ` Theodore Ts'o
[not found] ` <Y1Hby38PE/QVlRhF@Slackware>
2022-10-21 6:11 ` Tanju Brunostar
-- strict thread matches above, loose matches on Subject: below --
2022-10-22 8:11 request " Tanju Brunostar
2022-10-22 8:13 ` Julia Lawall
2022-10-22 8:20 ` Tanju Brunostar
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=Y1E6qYkzkRxlloNp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@gmail.com \
--cc=unixbhaskar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox