Date:   Tue, 7 Mar 2023 09:18:36 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Khadija <kamrankhadijadj@gmail.com>
Cc:     Dan Carpenter <error27@gmail.com>, outreachy@lists.linux.dev,
        linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: axis-fifo: alignment should match opening
 parenthesis in axis-fifo.c
Message-ID: <ZAbzXA5+tMaagtFj@kroah.com>
References: <ZAZSmPpB6fcozGa4@khadija-virtual-machine>
 <9543f943-759f-4e87-8f88-4eba7c1e4785@kili.mountain>
 <CACcTnM5kVTG3JaLK9mjaOO7qcXoTrb4xsg2af5Ac1ScqFfbjTg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACcTnM5kVTG3JaLK9mjaOO7qcXoTrb4xsg2af5Ac1ScqFfbjTg@mail.gmail.com>
Precedence: bulk

On Tue, Mar 07, 2023 at 01:10:17PM +0500, Khadija wrote:
> Hey Dan! Thank you for your feedback.
> Yes, the code currently looks unreadable. I am making changes and resending
> the patch.
> Also, on running checkpatch.pl on my patch file I get a warning about 75
> chars per line. Is there a way of fixing it automatically using script?

Hi,

Minor housekeeping notes.  Your email client is sending out html email,
which is rejected by the public mailing lists.  Please reconfigure it to
not do that.

Also, try not to ever top-post like this, it breaks the review process
and makes it impossible at times to determine what you are actually
responding back to.  Read some of the mailing list archives at
lore.kernel.org for examples of the proper way to respond to messages
inline.

thanks,

greg k-h