From: Jes Sorensen <jes.sorensen@gmail.com>
To: Vaishali Thakkar <vthakkar1994@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: rtl8188eu: Use put_unaligned_le16
Date: Fri, 20 Feb 2015 07:01:00 -0500 [thread overview]
Message-ID: <54E721FC.6080301@gmail.com> (raw)
In-Reply-To: <CAK-LDbKy8zE9kz_48Ja8wtX6G+xhDZvr4KxpXnQG9H=tw+L5Zg@mail.gmail.com>
On 02/19/15 03:43, Vaishali Thakkar wrote:
> On Thu, Feb 19, 2015 at 1:58 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Thursday 19 February 2015 08:35:46 Vaishali Thakkar wrote:
>>> On Feb 19, 2015 4:01 AM, "Jes Sorensen" <jes.sorensen@gmail.com> wrote:
>>>>
>>>> The key is to make the changes in two commits. In general you can post
>>>> them as part of a multi-commit patch set if you are fixing something in
>>>> a large number of places, or changing an API etc. For more independent
>>>> changes like these, posting them individually is preferred.
>>>>
>>>> I hope this makes more sense.
>>>
>>> Yes. Ok. I will send this patch as a series of patches. One for
>>> put_unaligned_le16 function and other one for removing use of variable.
>>
>> There are lots of ways for splitting a patch series, and usually doing
>> a multiple smaller changes is better than combining them, but there is a
>> limit. In this case you have four changes that could be done separately:
>>
>> a) use put_unaligned_le16 in rtl8188eu
>> b) remove tim_bitmap_le variable in rtl8188eu
>> c) use put_unaligned_le16 in rtl8723au
>> d) remove tim_bitmap_le variable in rtl8723au
>>
>> What Jes and I were saying is that you should do a) combined with b) as
>> one patch, and c) with d) as a second patch, but send them as a series,
>> not a) and c) combined as one patch followed by b) and d) as you understood.
>
> Oh. ok. Actually there is one misunderstanding here. I already sent 2 separate
> patches. First one combining a) and b) and second one combining c) and d).
> But after Jes's comment what I thought that he wants me to send 2 patch-series
> with 4 different patches where [ a) and b) ]goes for 1st patch-series
> and [c) and d) ]
> goes for 2nd patch-series. But thanks for clearing this.
>
> I will send a patch-series[ 2 patches- one patch for rtl8188eu and
> second for rtl8723au]
> as you explained.
Sorry for being ambiguous on this one, Arnd is absolutely right. The a+b
c+d solution is the right way - you are basically fixing up two small
closely related issues, so it is best to keep them together in the same
patch.
Cheers,
Jes
prev parent reply other threads:[~2015-02-20 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 4:42 [PATCH] Staging: rtl8188eu: Use put_unaligned_le16 Vaishali Thakkar
2015-02-17 9:02 ` [Outreachy kernel] " Arnd Bergmann
2015-02-17 10:11 ` Vaishali Thakkar
2015-02-17 19:12 ` Jes Sorensen
2015-02-18 1:32 ` Vaishali Thakkar
2015-02-18 10:50 ` Arnd Bergmann
2015-02-18 17:10 ` Jes Sorensen
2015-02-18 18:08 ` Vaishali Thakkar
2015-02-18 22:31 ` Jes Sorensen
2015-02-19 3:05 ` Vaishali Thakkar
2015-02-19 8:28 ` Arnd Bergmann
2015-02-19 8:43 ` Vaishali Thakkar
2015-02-20 12:01 ` Jes Sorensen [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=54E721FC.6080301@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=arnd@arndb.de \
--cc=outreachy-kernel@googlegroups.com \
--cc=vthakkar1994@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.