From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
Cc: dpenkler@gmail.com, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
kuba@kernel.org, rmk+kernel@armlinux.org.uk
Subject: Re: [PATCH v3 2/4] [PATCH V2 2/4] staging:gpib:agilent_82350b: Removed commented out code
Date: Mon, 17 Feb 2025 17:19:20 +0300 [thread overview]
Message-ID: <2ff8f3f8-e915-4ec0-80e8-fbc87c8fd1b2@stanley.mountain> (raw)
In-Reply-To: <CAEEw=4mN+Y8G6a92baCH6kANcpmTFDzn_LSS3XRfXAFdPZxo8A@mail.gmail.com>
On Mon, Feb 17, 2025 at 07:09:23PM +0530, Ravi Kumar Kairi wrote:
> So should I just do the whole deleting comment thing in one go? Instead of
> first deleted comment and then deleted blank space?
Hm... I had to check. All the issues addressed in patch 3 were
introduced by patch 2. So, yes, combine patch 2 and 3.
regards,
dan carpenter
next prev parent reply other threads:[~2025-02-17 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:30 [PATCH v3 0/4] staging:gpib:agilent_82350b: Code cleanup, spelling fixes Ravi Kumar kairi
2025-02-17 10:30 ` [PATCH v3 1/4] [PATCH V2 1/4] staging:gpib:agilent_82350b: Fixed spelling error Ravi Kumar kairi
2025-02-17 10:30 ` [PATCH v3 2/4] [PATCH V2 2/4] staging:gpib:agilent_82350b: Removed commented out code Ravi Kumar kairi
2025-02-17 13:31 ` Dan Carpenter
[not found] ` <CAEEw=4mN+Y8G6a92baCH6kANcpmTFDzn_LSS3XRfXAFdPZxo8A@mail.gmail.com>
2025-02-17 14:19 ` Dan Carpenter [this message]
2025-02-17 10:30 ` [PATCH v3 3/4] [PATCH V2 3/4] staging:gpib:agilent_82350b:Removed blank line Ravi Kumar kairi
2025-02-17 10:38 ` Greg KH
2025-02-17 10:30 ` [PATCH v3 4/4] [PATCH V2 4/4] staging:gpib:agilent_82350b: Fix Indent issue with block Ravi Kumar kairi
2025-02-17 10:39 ` Greg KH
2025-02-17 11:01 ` Ravi Kumar Kairi
2025-02-17 10:37 ` [PATCH v3 0/4] staging:gpib:agilent_82350b: Code cleanup, spelling fixes Greg KH
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=2ff8f3f8-e915-4ec0-80e8-fbc87c8fd1b2@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kumarkairiravi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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