Linux kernel staging patches
 help / color / mirror / Atom feed
From: Khadija Kamran <kamrankhadijadj@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
	outreachy@lists.linux.dev,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: axis-fifo: initialize read_timeout and write_timeout once in probe function
Date: Mon, 13 Mar 2023 23:26:03 +0500	[thread overview]
Message-ID: <ZA9qu+E/gPZ68mw4@khadija-virtual-machine> (raw)
In-Reply-To: <ZA9ZY91K8iQtn0ev@aschofie-mobl2>

On Mon, Mar 13, 2023 at 10:12:03AM -0700, Alison Schofield wrote:
> 
> It sounds like the git commit hook for checkpatch, suggested in
> the tutorial, would have saved you here. Please look that up.
>

Hey Alison!
I had set up git post-commit hook following the tutorial. The script
showed the errors, but I ignored them before. I have submitted another
patch. I had 'trailing white spaces' errors in my code and removed them
in the new patch after consultation from 'coding-style.rst' file.

> Also see the section "Following the Driver commit style"
> And, there are sections on revising patchsets too.
> 
> Much of the info in the tutorial doesn't make sense until you
> need it. So, keep reviewing it to catch more useful info.
>

Yes!! No matter how many times I read the tutorial, I still end up
getting back to it! :)
Thank you!

Regards,
Khadija

> More on running checkpatch:
> - Add that git commmit hook.
> - The final checkpatch run can be on the formatted patches.
>   After you've done git format-patch and have a .patch file you
>   are thinking of sending, run it again. 
> 
> Something like this:
> scripts/checkpatch.pl --no-tree --strict --codespellfile=/usr/bin/codespell ~/my_patches/*.patch
> 
> > 
> > Also, I had one question. Is it okay to write a long subject as I have
> > used in this patch? 
> This is in the tutorial. section "Following the Driver commit style"
>
> > 
> > Regards,
> > Khadija
> > 
> > > >  drivers/staging/axis-fifo/axis-fifo.c | 18 ++++++++++++------
> > > >  1 file changed, 12 insertions(+), 6 deletions(-)
> > > 
> > > 
> > > 
> > 

      reply	other threads:[~2023-03-13 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 17:33 [PATCH v4] staging: axis-fifo: initialize read_timeout and write_timeout once in probe function Khadija Kamran
2023-03-13  6:37 ` Greg Kroah-Hartman
2023-03-13 14:13 ` Fabio M. De Francesco
2023-03-13 14:48   ` Khadija Kamran
2023-03-13 15:04     ` Dan Carpenter
2023-03-13 15:18       ` Khadija Kamran
2023-03-13 17:12     ` Alison Schofield
2023-03-13 18:26       ` Khadija Kamran [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=ZA9qu+E/gPZ68mw4@khadija-virtual-machine \
    --to=kamrankhadijadj@gmail.com \
    --cc=alison.schofield@intel.com \
    --cc=fmdefrancesco@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