From: Pavan Chebbi <pavan.chebbi@broadcom.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: 3chas3@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-atm-general@lists.sourceforge.net
Subject: Re: [PATCH] atm: iphase: Fix a typo in printk message.
Date: Sun, 25 Dec 2022 22:12:23 +0530 [thread overview]
Message-ID: <CALs4sv3xd8HAhz5DY9MwyQtVMsv_o-4AoFh6P6xkmYff7_r4dw@mail.gmail.com> (raw)
In-Reply-To: <20221223074135.150076-1-standby24x7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Fri, Dec 23, 2022 at 1:11 PM Masanari Iida <standby24x7@gmail.com> wrote:
>
> This patch fixes a spelling typo in printk message.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> drivers/atm/iphase.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/atm/iphase.c b/drivers/atm/iphase.c
> index 324148686953..aea5fc4c206e 100644
> --- a/drivers/atm/iphase.c
> +++ b/drivers/atm/iphase.c
> @@ -549,7 +549,7 @@ static int ia_cbr_setup (IADEV *dev, struct atm_vcc *vcc) {
> if (testSlot >= (int)dev->CbrTotEntries) { // Wrap if necessary
> testSlot -= dev->CbrTotEntries;
> IF_CBR(printk("TotCbrEntries=%d",dev->CbrTotEntries);)
> - IF_CBR(printk(" Testslot=0x%x ToBeAssgned=%d\n",
> + IF_CBR(printk(" Testslot=0x%x ToBeAssigned=%d\n",
> testSlot, toBeAssigned);)
I think current checkpatch errors are valid even though the original
code may be violating. You may fix them and also add a fixes tag.
> }
> // set table index and read in value
> --
> 2.38.1
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]
prev parent reply other threads:[~2022-12-25 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 7:41 [PATCH] atm: iphase: Fix a typo in printk message Masanari Iida
2022-12-25 16:42 ` Pavan Chebbi [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=CALs4sv3xd8HAhz5DY9MwyQtVMsv_o-4AoFh6P6xkmYff7_r4dw@mail.gmail.com \
--to=pavan.chebbi@broadcom.com \
--cc=3chas3@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=standby24x7@gmail.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 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).