From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-mtd@lists.infradead.org,
Laurent Pichart <laurent.pinchart@ideasonboard.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 1/7] mtd: sh_flctl: Expand FLCMNCR register bit field
Date: Fri, 09 Mar 2012 14:48:51 +0200 [thread overview]
Message-ID: <1331297331.29445.19.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1330595321-2728-1-git-send-email-hechtb@gmail.com>
On Thu, 2012-03-01 at 10:48 +0100, Bastian Hecht wrote:
> Add support for a new hardware generation. The meaning of some bits
> of the FLCMNCR register changed, so some new defines are added
> parallel to the existing ones to keep backward compatibility.
>
> The defines allow to choose an appropriate clocking scheme.
>
> Signed-off-by: Bastian Hecht <hechtb@gmail.com>
Pushed the patch-set to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-mtd@lists.infradead.org,
Laurent Pichart <laurent.pinchart@ideasonboard.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 1/7] mtd: sh_flctl: Expand FLCMNCR register bit field
Date: Fri, 09 Mar 2012 12:48:51 +0000 [thread overview]
Message-ID: <1331297331.29445.19.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1330595321-2728-1-git-send-email-hechtb@gmail.com>
On Thu, 2012-03-01 at 10:48 +0100, Bastian Hecht wrote:
> Add support for a new hardware generation. The meaning of some bits
> of the FLCMNCR register changed, so some new defines are added
> parallel to the existing ones to keep backward compatibility.
>
> The defines allow to choose an appropriate clocking scheme.
>
> Signed-off-by: Bastian Hecht <hechtb@gmail.com>
Pushed the patch-set to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2012-03-09 12:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 9:48 [PATCH v3 1/7] mtd: sh_flctl: Expand FLCMNCR register bit field Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 2/7] mtd: sh_flctl: Reorder empty_fifo() calls Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 3/7] mtd: sh_flctl: Expand the READID command to 8 bytes Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 4/7] mtd: sh_flctl: Implement NAND_CMD_RNDOUT command Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 5/7] mtd: sh_flctl: Use cached register value for FLCMNCR Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 6/7] mtd: sh_flctl: Add FLHOLDCR register Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 9:48 ` [PATCH v3 7/7] ARM: mach-shmobile: mackerel: Add the flash controller flctl Bastian Hecht
2012-03-01 9:48 ` Bastian Hecht
2012-03-01 15:19 ` [PATCH v3 1/7] mtd: sh_flctl: Expand FLCMNCR register bit field Laurent Pinchart
2012-03-01 15:19 ` Laurent Pinchart
2012-03-09 12:48 ` Artem Bityutskiy [this message]
2012-03-09 12:48 ` Artem Bityutskiy
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=1331297331.29445.19.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=hechtb@googlemail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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.