All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: shuah@kernel.org, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, socketcan@hartkopp.net,
	mkl@pengutronix.de, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	corbet@lwn.net
Subject: Re: [PATCH] documentation: networking: fix spelling mistakes
Date: Sat, 25 Jan 2025 14:11:30 +0200	[thread overview]
Message-ID: <5248fbae-982e-4efa-9481-5e2ded2b4443@gmail.com> (raw)
In-Reply-To: <69da3515-13c8-4626-a2b8-cce7c625da43@intel.com>

On 1/23/25 11:12 AM, Przemek Kitszel wrote:

> looks good, also process wise, also this comment is properly put
> (one thing to possibly improve would be to put "net" as the target in
> the subject (see other patches on the netdev mailing list); for
> non-fixes it would be "net-next"; but don't resubmit just for that)

Ahaa, I also should not have sent this patch during a merge
window where net-next is closed?

Thank you for the heads up, I will be spending more time with
https://docs.kernel.org/process/maintainer-netdev.html

> I'm assuming you have fixed all the typos in that two files, with that:
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>

Yes that was all I could find in these two files.

Thanks,
Khaled


  reply	other threads:[~2025-01-25 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  8:25 [PATCH] documentation: networking: fix spelling mistakes Khaled Elnaggar
2025-01-23  8:37 ` Marc Kleine-Budde
2025-01-23  9:12 ` Przemek Kitszel
2025-01-25 12:11   ` Khaled Elnaggar [this message]
2025-01-27  8:16     ` Przemek Kitszel
2025-01-27 10:52       ` Khaled Elnaggar
2025-01-23 17:15 ` Randy Dunlap
2025-01-24 10:02 ` Bagas Sanjaya
  -- strict thread matches above, loose matches on Subject: below --
2025-02-17  7:07 [PATCH] documentation : networking : Fix " Chandra Mohan Sundar

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=5248fbae-982e-4efa-9481-5e2ded2b4443@gmail.com \
    --to=khaledelnaggarlinux@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shuah@kernel.org \
    --cc=socketcan@hartkopp.net \
    /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.