From: Alison Schofield <alison.schofield@intel.com>
To: Raghu Halharvi <raghuhack78@gmail.com>
Cc: linux-cxl@vger.kernel.org, ira.weiny@intel.com,
bwidawsk@kernel.org, dan.j.williams@intel.com,
vishal.l.verma@intel.com, linux-kernel@vger.kernel.org,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH RESEND v6 0/2] Fixing check patch styling issues
Date: Tue, 25 Jul 2023 10:55:41 -0700 [thread overview]
Message-ID: <ZMAMnd8Pg5vGKKH7@aschofie-mobl2> (raw)
In-Reply-To: <20230725121930.3732-1-raghuhack78@gmail.com>
On Tue, Jul 25, 2023 at 12:19:28PM +0000, Raghu Halharvi wrote:
> v6 changes:
> - PATCH RESEND, the v5 was approved was not committed, Ira suggested to
> resend both patches.
Hi Raghu,
If this was a true RESEND, the version number should not have changed.
See: Documentation/process/submitting-patches.rst
Alas, this v6 has changes from v5 that are not listed here, so this
is not a RESEND, it is a new version.
Both patches were rebased, and in Patch 1 that led to a changed
function name too.
What to do?
How about you send a reply to this cover letter with the v5->v6
changelog, and let's see if that's clear enough.
Thanks,
Alison
>
> v5 changes:
> - Updated the missing reviewed tag in "cxl/mbox: Remove redundant
> dev_err() after failed mem alloc" patch (Dave Jiang)
>
> v4 changes:
> - Updated the respective patches with reviewers tags for respective
> patches(Dave Jiang)
>
> v3 changes:
> - Update the cover letter and commit message with full author
> name(Fabio/Alison)
> - Correct the "typo error" in commit message(Fabio)
>
> v2 changes:
> Thanks Alison, Ira for your comments, modified the v1 patches as
> suggested.
> Dropped the patch containing tab changes in port.c
>
> v1 cover letter:
> The following patches are cleanup or fixing the styling issues found
> using checkpatch
>
> In cxl/core/mbox.c, in case of null check failure, returning errno or
> -ENOMEM in this case is good enough, removing the redundant dev_err
> message.
>
> In cxl/core/region.c, the else is not required after the return
> statement, cleaned it up.
>
> Verified the build and sanity by booting the guest VM using the freshly
> built components.
>
> Raghu Halharvi (2):
> cxl/mbox: Remove redundant dev_err() after failed mem alloc
> cxl/region: Remove else after return statement
>
> drivers/cxl/core/mbox.c | 4 +---
> drivers/cxl/core/region.c | 8 ++++----
> 2 files changed, 5 insertions(+), 7 deletions(-)
>
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-07-25 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 12:19 [PATCH RESEND v6 0/2] Fixing check patch styling issues Raghu Halharvi
2023-07-25 12:19 ` [PATCH RESEND v6 1/2] cxl/mbox: Remove redundant dev_err() after failed mem alloc Raghu Halharvi
2023-07-25 12:19 ` [PATCH RESEND v6 2/2] cxl/region: Remove else after return statement Raghu Halharvi
2023-07-25 17:55 ` Alison Schofield [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-25 19:43 [PATCH RESEND v6 0/2] Fixing check patch styling issues Raghu Halharvi
2023-07-26 3:45 ` Alison Schofield
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=ZMAMnd8Pg5vGKKH7@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raghuhack78@gmail.com \
--cc=vishal.l.verma@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.