From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 23/23 V2 for 3.19] rtlwifi: Fix error when accessing unmapped memory in skb
Date: Tue, 06 Jan 2015 10:10:26 +0200 [thread overview]
Message-ID: <871tn81g99.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54AB0145.3070601@lwfinger.net> (Larry Finger's message of "Mon, 05 Jan 2015 15:25:25 -0600")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> On 01/05/2015 03:20 AM, Kalle Valo wrote:
>> Larry Finger <Larry.Finger@lwfinger.net> writes:
>>
>>>> 23/23? Where are patches 1-22? I don't see them in patchwork:
>>>>
>>>> https://patchwork.kernel.org/project/linux-wireless/list/
>>>
>>> Sorry. I forgot to edit the subject line. To get git to format that
>>> one patch, I had to generate a total of 23. There is only 1 of 1 that
>>> will be submitted.
>>
>> Ok, I was just worried that I had missed the other 22. But you can
>> actually get a single commit like this so no editing is needed:
>>
>> git format-patch -1 2a3e60d37fc6
>
> Thanks for the git lesson. Some week^H^H^H^Hmonth I should learn to
> use more parts of that tool, but you know how that goes.
I have the exactly same situation with python :)
> I do have an additional question on procedure. If I submit a number of
> patches in a series, but find that only one of the series needs a V2.
> Is it better to resubmit all N of them, or only just the one that
> needs changing?
Please resubmit the whole series. It's just so much easier and more
reliable for me to handle changes that way.
--
Kalle Valo
next prev parent reply other threads:[~2015-01-06 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 20:17 [PATCH 23/23 V2 for 3.19] rtlwifi: Fix error when accessing unmapped memory in skb Larry Finger
2014-12-28 5:50 ` Kalle Valo
2014-12-28 6:15 ` Larry Finger
2015-01-05 9:20 ` Kalle Valo
2015-01-05 21:25 ` Larry Finger
2015-01-06 8:10 ` Kalle Valo [this message]
2014-12-31 0:49 ` Eric Biggers
2014-12-31 3:31 ` Larry Finger
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=871tn81g99.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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).