From: Simon Horman <horms@kernel.org>
To: yanzhen <11171358@vivo.com>
Cc: Yan Zhen <yanzhen@vivo.com>,
3chas3@gmail.com, linux-atm-general@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
opensource.kernel@vivo.com
Subject: Re: [PATCH v1] atm: Fix typo in the comment
Date: Fri, 27 Sep 2024 19:31:40 +0100 [thread overview]
Message-ID: <20240927183140.GM4029621@kernel.org> (raw)
In-Reply-To: <812b36ac-2fcc-4107-99ad-a44e3e2eda71@vivo.com>
On Fri, Sep 27, 2024 at 04:22:19PM +0800, yanzhen wrote:
>
> 在 2024/9/26 4:05, Simon Horman 写道:
> > On Wed, Sep 25, 2024 at 06:57:07PM +0800, Yan Zhen wrote:
> > > Correctly spelled comments make it easier for the reader to understand
> > > the code.
> > >
> > > Fix typos:
> > > 'behing' ==> 'being',
> > > 'useable' ==> 'usable',
> > > 'arry' ==> 'array',
> > > 'receieve' ==> 'receive',
> > > 'desriptor' ==> 'descriptor',
> > > 'varients' ==> 'variants',
> > > 'recevie' ==> 'receive',
> > > 'Decriptor' ==> 'Descriptor',
> > > 'Lable' ==> 'Label',
> > > 'transmiting' ==> 'transmitting',
> > > 'correspondance' ==> 'correspondence',
> > > 'claculation' ==> 'calculation',
> > > 'everone' ==> 'everyone',
> > > 'contruct' ==> 'construct'.
> > >
> > >
> > > Signed-off-by: Yan Zhen <yanzhen@vivo.com>
> > Hi,
> >
> > I am curious to know which tree is this based on?
> > I don't seem to be able to apply it to net-next, linux-net,
> > or Linus's tree.
> I apologize, I may not have generated the patch based on the latest branch.
> Is the net-next branch currently closed? Should I wait for it to reopen
> before submitting?
Yes, net-next is currently closed.
And yes, I think it would be best to wait for it to reopen.
I expect that will happen next week.
--
pw-bot: defer
prev parent reply other threads:[~2024-09-27 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 10:57 [PATCH v1] atm: Fix typo in the comment Yan Zhen
2024-09-25 20:05 ` Simon Horman
2024-09-27 8:22 ` yanzhen
2024-09-27 18:31 ` Simon Horman [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=20240927183140.GM4029621@kernel.org \
--to=horms@kernel.org \
--cc=11171358@vivo.com \
--cc=3chas3@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=yanzhen@vivo.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.