From: Sumitra Sharma <sumitraartsy@gmail.com>
To: outreachy@lists.linux.dev
Cc: julia.lawall@inria.fr, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: pi433: Change bit_rate type from u16 to u32
Date: Sat, 11 Mar 2023 03:59:04 -0800 [thread overview]
Message-ID: <20230311115904.GA21529@ubuntu> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2303111249470.2802@hadrien>
Hi julia,
I forgot to Cc the maintainers of the code of the above patch. I have Cc
in this mail. Do let me know if there is a need of recreating the patch.
next prev parent reply other threads:[~2023-03-11 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 11:42 [PATCH] Staging: pi433: Change bit_rate type from u16 to u32 Sumitra Sharma
2023-03-11 11:50 ` Julia Lawall
2023-03-11 11:59 ` Sumitra Sharma [this message]
2023-03-11 12:12 ` Julia Lawall
2023-03-13 1:34 ` Ira Weiny
-- strict thread matches above, loose matches on Subject: below --
2023-03-11 12:23 Sumitra Sharma
2023-03-11 12:31 ` Greg KH
2023-03-11 12:39 ` Dan Carpenter
2023-03-11 13:00 ` Sumitra Sharma
2023-03-11 13:17 ` Dan Carpenter
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=20230311115904.GA21529@ubuntu \
--to=sumitraartsy@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--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 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.