From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] split code in mt76x02_util.{c,h}
Date: Mon, 8 Oct 2018 11:16:02 +0200 [thread overview]
Message-ID: <20181008091601.GA15297@localhost.localdomain> (raw)
In-Reply-To: <1538987449.3687.1.camel@sipsolutions.net>
> Lorenzo,
>
Hi Johannes,
> It would help - also for patchwork tracking - if you could thread your
> patch series properly.
>
> FWIW, that should be the default in git send-email, so I think you need
> to either update your version or change its configuration. Unless you
> weren't using --compose option and sent the 0/N manually beforehand or
> something?
>
I sent this series from a different machine so I guess it is not configured
properly, I will double check. Thx for the info.
Regards,
Lorenzo
> johannes
>
> On Tue, 2018-10-02 at 00:34 +0200, Lorenzo Bianconi wrote:
prev parent reply other threads:[~2018-10-08 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 22:34 [PATCH 0/3] split code in mt76x02_util.{c,h} Lorenzo Bianconi
2018-10-08 8:30 ` Johannes Berg
2018-10-08 9:16 ` Lorenzo Bianconi [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=20181008091601.GA15297@localhost.localdomain \
--to=lorenzo.bianconi@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--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 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.