From: Lars Poeschel <poeschel-Xtl8qvBWbHwb1SvskN2V4Q@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC] misc/at24: distinguish between eeprom and fram chips
Date: Wed, 6 Feb 2013 19:19:18 +0100 [thread overview]
Message-ID: <201302061919.18501.poeschel@lemonage.de> (raw)
In-Reply-To: <20121205164153.GA5011-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Wednesday 05 December 2012 at 17:41:53, Wolfram Sang wrote:
> > > The method of accessing EEPROMs is used by way more chips than FRAMs.
> > > So, I'd prefer to have the text updated more generic like "EEPROMs and
> > > similar devices like RAMs, ROMs, etc...". Describing setting .flags in
> > > Kconfig is overkill.
> >
> > A patch updating Kconfig is below.
>
> Looks good from a glimpse, will apply it later.
Hello Wolfram,
what happend to this one ? It was a patch updating Kconfig help for at24.
https://patchwork.kernel.org/patch/1840591/
Regards,
Lars
next prev parent reply other threads:[~2013-02-06 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 16:58 [PATCH RFC] misc/at24: distinguish between eeprom and fram chips Lars Poeschel
2012-12-04 18:32 ` Wolfram Sang
[not found] ` <20121204183238.GA15067-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-12-05 9:43 ` Lars Poeschel
[not found] ` <201212051043.07460.poeschel-Xtl8qvBWbHwb1SvskN2V4Q@public.gmane.org>
2012-12-05 16:41 ` Wolfram Sang
[not found] ` <20121205164153.GA5011-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-12-07 10:14 ` Lars Poeschel
2013-01-24 7:27 ` Wolfram Sang
2013-01-28 10:40 ` Lars Poeschel
2013-02-06 18:19 ` Lars Poeschel [this message]
[not found] ` <201302061919.18501.poeschel-Xtl8qvBWbHwb1SvskN2V4Q@public.gmane.org>
2013-02-10 16:30 ` Wolfram Sang
2013-02-11 8:51 ` Lars Poeschel
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=201302061919.18501.poeschel@lemonage.de \
--to=poeschel-xtl8qvbwbhwb1svskn2v4q@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).