From: David Miller <davem@davemloft.net>
To: mail@maciej.szmigiero.name
Cc: isdn@linux-pingi.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mISDN: Order IPAC register defines
Date: Mon, 14 Mar 2016 15:51:47 -0400 (EDT) [thread overview]
Message-ID: <20160314.155147.1140508735160132410.davem@davemloft.net> (raw)
In-Reply-To: <56E4A3AE.8050407@maciej.szmigiero.name>
From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Date: Sun, 13 Mar 2016 00:18:06 +0100
> It looks like IPAC/ISAC chips register defines weren't in any particular
> order.
>
> Order them by their number to make it easier to spot holes.
>
> Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Applied.
prev parent reply other threads:[~2016-03-14 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 23:18 [PATCH 1/2] mISDN: Order IPAC register defines Maciej S. Szmigiero
2016-03-13 3:13 ` isdn
2016-03-14 19:51 ` David Miller [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=20160314.155147.1140508735160132410.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=netdev@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).