linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tong Zhang <ztong0001@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	H Hartley Sweeten <hsweeten@visionengravers.com>,
	Ian Abbott <abbotti@mev.co.uk>,
	devel@driverdev.osuosl.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: comedi: das800: fix request_irq() warn
Date: Wed, 17 Mar 2021 18:43:31 -0400	[thread overview]
Message-ID: <CAA5qM4Bc5tW9QmeC7MKCO7yivxQrSfgVBwgyFLhipK9w=q7Scg@mail.gmail.com> (raw)
In-Reply-To: <20210317065248.GW21246@kadam>

Thanks for sharing those best practices, Dan.
I was wondering if there is a spelling checker for git.

  reply	other threads:[~2021-03-17 22:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14  3:57 [PATCH] staging: comedi: replace slash in name Tong Zhang
2021-03-15 10:44 ` Ian Abbott
2021-03-15 10:48   ` Ian Abbott
2021-03-15 19:58     ` [PATCH v2] staging: comedi: cb_pcidas64: fix request_irq() warn Tong Zhang
2021-03-16 10:31       ` Ian Abbott
2021-03-15 20:00     ` [PATCH] staging: comedi: replace slash in name Tong Zhang
2021-03-16 10:37       ` Ian Abbott
2021-03-16 22:42         ` [PATCH] staging: comedi: das800: fix request_irq() warn Tong Zhang
2021-03-17  5:14           ` Dan Carpenter
     [not found]             ` <CAA5qM4BcQ6+aa1C3_28zLVojwLduK-WZwsEftuasJgo8z0t0ew@mail.gmail.com>
2021-03-17  6:52               ` Dan Carpenter
2021-03-17 22:43                 ` Tong Zhang [this message]
2021-03-17 12:48           ` Ian Abbott
2021-03-19  3:47             ` [PATCH v2] " Tong Zhang
2021-03-19  3:48             ` [PATCH] " Tong Zhang
2021-03-16 22:42         ` [PATCH] staging: comedi: replace slash in name Tong Zhang

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='CAA5qM4Bc5tW9QmeC7MKCO7yivxQrSfgVBwgyFLhipK9w=q7Scg@mail.gmail.com' \
    --to=ztong0001@gmail.com \
    --cc=abbotti@mev.co.uk \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=grandmaster@al2klimov.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsweeten@visionengravers.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).