All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: [RFC PATCH v2] can: sja1000: use common prefix for all sja1000 defines
Date: Tue, 16 Apr 2013 12:40:59 +0200	[thread overview]
Message-ID: <516D2ABB.4000300@pengutronix.de> (raw)
In-Reply-To: <5169B395.2070703@hartkopp.net>

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

On 04/13/2013 09:35 PM, Oliver Hartkopp wrote:
> This is a follow up patch to:
> 
>     f901b6b can: sja1000: fix define conflict on SH
> 
> That patch fixed a define conflict between the SH architecture and the sja1000
> driver, by addind a prefix to one macro only. This patch consistently renames
> the prefix of the SJA1000 controller registers from "REG_" to "SJA1000_".
> 
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> 
> ---
> 
> Hello Marc,
> 
> to not miss the current net-next window, here's a well formatted patch for my
> REG_ rename proposal. It renames the formerly register defines from REG_ to
> SJA1000_ and leaves the content definitions of the registers as-is.
> This is because of all content definitions would have to be changed in 
> sja1000.h AND include/linux/can/platform/sja1000.h to have a consistent
> naming scheme.

Looks good, I've fixed the indention in
drivers/net/can/sja1000/sja1000.h. I'll send a pull request to David soon.

Thanks, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-04-16 10:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 19:35 [RFC PATCH v2] can: sja1000: use common prefix for all sja1000 defines Oliver Hartkopp
2013-04-16 10:40 ` Marc Kleine-Budde [this message]
2013-04-24  9:06   ` Is there any way of getting the CAN interfaces list, from any C program? Stephane Grosjean
2013-04-24 14:49     ` Kurt Van Dijck
2013-04-25  6:41       ` Wolfgang Grandegger
2013-04-25  7:07         ` Marc Kleine-Budde
2013-04-25  7:35           ` Marc Kleine-Budde
2013-04-25  9:15             ` Kurt Van Dijck
2013-04-25  9:20               ` Marc Kleine-Budde
2013-04-25  7:24         ` Kurt Van Dijck
2013-04-25  7:43           ` Wolfgang Grandegger
2013-04-25  9:14             ` Kurt Van Dijck
2013-04-25  9:23               ` Marc Kleine-Budde
2013-04-25  9:42                 ` Kurt Van Dijck
2013-04-25 21:08                   ` Kurt Van Dijck
2013-04-24 21:02     ` François
2013-04-24 21:27       ` Marc Kleine-Budde
2013-04-25  8:04       ` Kurt Van Dijck

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=516D2ABB.4000300@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.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.