linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [RESEND PATCH 1/9] eeprom: at24: platform_data: use BIT() macro
Date: Tue, 20 Oct 2015 10:43:19 +0200	[thread overview]
Message-ID: <1445330607-12470-2-git-send-email-bgolaszewski@baylibre.com> (raw)
In-Reply-To: <1445330607-12470-1-git-send-email-bgolaszewski@baylibre.com>

Use BIT() macro to replace the 0xXX constants in platform_data flags
definitions.

Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
 include/linux/platform_data/at24.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/include/linux/platform_data/at24.h b/include/linux/platform_data/at24.h
index c42aa89..8d90f52 100644
--- a/include/linux/platform_data/at24.h
+++ b/include/linux/platform_data/at24.h
@@ -43,10 +43,10 @@ struct at24_platform_data {
 	u32		byte_len;		/* size (sum of all addr) */
 	u16		page_size;		/* for writes */
 	u8		flags;
-#define AT24_FLAG_ADDR16	0x80	/* address pointer is 16 bit */
-#define AT24_FLAG_READONLY	0x40	/* sysfs-entry will be read-only */
-#define AT24_FLAG_IRUGO		0x20	/* sysfs-entry will be world-readable */
-#define AT24_FLAG_TAKE8ADDR	0x10	/* take always 8 addresses (24c00) */
+#define AT24_FLAG_ADDR16	BIT(7)	/* address pointer is 16 bit */
+#define AT24_FLAG_READONLY	BIT(6)	/* sysfs-entry will be read-only */
+#define AT24_FLAG_IRUGO		BIT(5)	/* sysfs-entry will be world-readable */
+#define AT24_FLAG_TAKE8ADDR	BIT(4)	/* take always 8 addresses (24c00) */
 
 	void		(*setup)(struct memory_accessor *, void *context);
 	void		*context;
-- 
2.1.4

  reply	other threads:[~2015-10-20  8:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  8:43 [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read Bartosz Golaszewski
2015-10-20  8:43 ` Bartosz Golaszewski [this message]
2015-10-20  8:43 ` [RESEND PATCH 2/9] eeprom: at24: new flag in platform_data Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 3/9] eeprom: at24: tie up an additional address for at24cs series Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 4/9] eeprom: at24: support reading of the serial number Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 5/9] eeprom: at24: export the serial number through sysfs Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 6/9] eeprom: at24: improve the device_id table readability Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 7/9] eeprom: at24: add the at24cs series to the list of supported devices Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 8/9] eeprom: at24: remove a reduntant if Bartosz Golaszewski
2015-10-20  8:43 ` [RESEND PATCH 9/9] eeprom: at24: readability tweaks Bartosz Golaszewski
2015-10-21 11:03 ` [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read Peter Korsgaard
2015-10-21 14:15   ` Bartosz Golaszewski
2015-10-21 14:23     ` Peter Korsgaard
2015-10-21 14:42       ` Bartosz Golaszewski
2015-10-21 15:08         ` Peter Korsgaard

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=1445330607-12470-2-git-send-email-bgolaszewski@baylibre.com \
    --to=bgolaszewski@baylibre.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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).