From: Dan Carpenter <dan.carpenter@oracle.com>
To: Bryan Brattlof <bb@ti.com>
Cc: Alaa Mohamed <eng.alaamohamedsoliman.am@gmail.com>,
outreachy@lists.linux.dev, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: Fix No space before tabs
Date: Thu, 31 Mar 2022 17:23:23 +0300 [thread overview]
Message-ID: <20220331142323.GQ3293@kadam> (raw)
In-Reply-To: <20220331133744.lypehhmz2wxngvzl@bryanbrattlof.com>
On Thu, Mar 31, 2022 at 08:37:44AM -0500, Bryan Brattlof wrote:
> > -/* Created by Roger, 2008.10.21. */
> > +/* Created by Roger, 2008.10.21. */
> > /* */
> > -/* 2008/12/12 MH 1. Reorganize code flow and reserve bytes. and add description. */
> > -/* 2. Add efuse utilization collect. */
> > -/* 2008/12/22 MH Read Efuse must check if we write section 1 data again!!! Sec1 */
> > -/* write addr must be after sec5. */
> > +/* 2008/12/12 MH 1. Reorganize code flow and reserve bytes. and add description. */
> > +/* 2. Add efuse utilization collect. */
> > +/* 2008/12/22 MH Read Efuse must check if we write section 1 data again!!! Sec1 */
> > +/* write addr must be after sec5. */
> > /* */
> >
>
> I'm wondering if it would be OK if we removed the change history and
> tried to align the indentation a little. (This may need to be multiple
> patches depending on how everyone else feels)
Yep. Feel free to delete the historical info.
regards,
dan carpenter
prev parent reply other threads:[~2022-03-31 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 13:09 [PATCH] staging: rtl8723bs: Fix No space before tabs Alaa Mohamed
2022-03-31 13:37 ` Bryan Brattlof
2022-03-31 14:23 ` Dan Carpenter [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=20220331142323.GQ3293@kadam \
--to=dan.carpenter@oracle.com \
--cc=bb@ti.com \
--cc=eng.alaamohamedsoliman.am@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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