All of lore.kernel.org
 help / color / mirror / Atom feed
From: "<gregkh@linuxfoundation.org>" <gregkh@linuxfoundation.org>
To: "Franziska Näpelt" <franziska.naepelt@googlemail.com>
Cc: eperi1024@gmail.com,
	"Franziska Näpelt" <franziska.naepelt@gmail.com>,
	hdegoede@redhat.com, johannes.berg@intel.com,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
	philipp.g.hortmann@gmail.com, quic_vjakkam@quicinc.com,
	tegongkang@gmail.com
Subject: Re: [PATCH v2 0/5] Fix some checkpatch issues
Date: Sun, 25 Jun 2023 15:55:40 +0200	[thread overview]
Message-ID: <2023062527-bride-unsolved-3b56@gregkh> (raw)
In-Reply-To: <F9C4E29E-C355-4B08-A2EC-2197A6EB7AFD@googlemail.com>

On Sun, Jun 25, 2023 at 03:33:59PM +0200, Franziska Näpelt wrote:
> Thanks for your feedback :)
> Since not all the patches of my first patch series have been applied, I thought I have to submit the whole series again. Submitting a series of 5 patches, where 3 have been already applied of course fails.
> So does it mean, if 3 of 5 patches of a series have been applied and I want to submit a new version, I only submit patches for the remaining work and not all of them again?

Yes, just submit the remaining ones.

thanks,

greg k-h

  parent reply	other threads:[~2023-06-25 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 13:33 [PATCH v2 0/5] Fix some checkpatch issues Franziska Näpelt
2023-06-25 13:53 ` Philipp Hortmann
2023-06-25 13:55 ` <gregkh@linuxfoundation.org> [this message]
2023-06-25 16:31   ` Franziska Näpelt
  -- strict thread matches above, loose matches on Subject: below --
2023-06-21 18:46 Franziska Naepelt
2023-06-23  8:18 ` Greg KH
2023-06-23 17:20   ` Philipp Hortmann
2023-06-24  6:50     ` Greg KH

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=2023062527-bride-unsolved-3b56@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=eperi1024@gmail.com \
    --cc=franziska.naepelt@gmail.com \
    --cc=franziska.naepelt@googlemail.com \
    --cc=hdegoede@redhat.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=quic_vjakkam@quicinc.com \
    --cc=tegongkang@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 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.