From: Brian Norris <computersforpeace@gmail.com>
To: vikas <vikas.manocha@st.com>
Cc: Marek Vasut <marex@denx.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Graham Moore <grmoore@opensource.altera.com>,
Alan Tull <atull@opensource.altera.com>,
David Woodhouse <dwmw2@infradead.org>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
Yves Vandervennet <yvanderv@opensource.altera.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller.
Date: Wed, 26 Aug 2015 11:06:31 -0700 [thread overview]
Message-ID: <20150826180631.GS81844@google.com> (raw)
In-Reply-To: <55DDDF99.4030701@st.com>
On Wed, Aug 26, 2015 at 08:47:37AM -0700, vikas wrote:
> On 08/25/2015 11:19 PM, Marek Vasut wrote:
> > On Wednesday, August 26, 2015 at 12:09:50 AM, vikas wrote:
> >> the patch failed to apply, please rebase it to master.
> >
> > it's based on -next, I'm sure you can fix trivial conflicts yourself if you
> > need to apply it elsewhere. Do you have any other review comments ?
>
> Always rebase the patch on master.
Development works against -next, not Linus' master:
https://lwn.net/Articles/289013/
This is also noted here:
https://www.kernel.org/doc/man-pages/linux-next.html
Technically, you should work off of the respective subsystem tree (see
entries in MAINTAINERS). For MTD, this is also documented here:
http://linux-mtd.infradead.org/source.html
In the end, most MTD patches get applied to l2-mtd.git, but l2-mtd.git
and linux-next.git should provide pretty similar MTD patching
experiences, as the former is included in the latter.
Regards,
Brian
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: vikas <vikas.manocha-qxv4g6HH51o@public.gmane.org>
Cc: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>,
"linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Graham Moore
<grmoore-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
Alan Tull
<atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Dinh Nguyen
<dinguyen-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
Yves Vandervennet
<yvanderv-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller.
Date: Wed, 26 Aug 2015 11:06:31 -0700 [thread overview]
Message-ID: <20150826180631.GS81844@google.com> (raw)
In-Reply-To: <55DDDF99.4030701-qxv4g6HH51o@public.gmane.org>
On Wed, Aug 26, 2015 at 08:47:37AM -0700, vikas wrote:
> On 08/25/2015 11:19 PM, Marek Vasut wrote:
> > On Wednesday, August 26, 2015 at 12:09:50 AM, vikas wrote:
> >> the patch failed to apply, please rebase it to master.
> >
> > it's based on -next, I'm sure you can fix trivial conflicts yourself if you
> > need to apply it elsewhere. Do you have any other review comments ?
>
> Always rebase the patch on master.
Development works against -next, not Linus' master:
https://lwn.net/Articles/289013/
This is also noted here:
https://www.kernel.org/doc/man-pages/linux-next.html
Technically, you should work off of the respective subsystem tree (see
entries in MAINTAINERS). For MTD, this is also documented here:
http://linux-mtd.infradead.org/source.html
In the end, most MTD patches get applied to l2-mtd.git, but l2-mtd.git
and linux-next.git should provide pretty similar MTD patching
experiences, as the former is included in the latter.
Regards,
Brian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-08-26 18:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 9:20 [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Marek Vasut
2015-08-21 9:20 ` Marek Vasut
2015-08-21 9:20 ` [PATCH 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Marek Vasut
2015-08-21 9:20 ` Marek Vasut
2015-08-25 22:09 ` vikas
2015-08-25 22:09 ` vikas
2015-08-26 6:19 ` Marek Vasut
2015-08-26 6:19 ` Marek Vasut
2015-08-26 15:47 ` vikas
2015-08-26 15:47 ` vikas
2015-08-26 16:39 ` Marek Vasut
2015-08-26 16:39 ` Marek Vasut
2015-08-26 18:06 ` Brian Norris [this message]
2015-08-26 18:06 ` Brian Norris
2015-08-26 23:05 ` vikas
2015-08-26 23:05 ` vikas
2015-08-31 17:30 ` Graham Moore
2015-08-31 17:30 ` Graham Moore
2015-08-31 22:36 ` Marek Vasut
2015-08-31 22:36 ` Marek Vasut
2015-09-04 23:45 ` vikas
2015-09-04 23:45 ` vikas
2015-09-06 15:16 ` Marek Vasut
2015-09-06 15:16 ` Marek Vasut
2015-09-07 18:56 ` vikas
2015-09-07 18:56 ` vikas
2015-09-07 20:27 ` vikas
2015-09-07 20:27 ` vikas
2015-10-15 14:10 ` Graham Moore
2015-10-15 14:10 ` Graham Moore
2015-10-15 14:27 ` Marek Vasut
2015-10-15 14:27 ` Marek Vasut
2016-01-11 4:14 ` [2/2] " R, Vignesh
2016-01-11 4:14 ` R, Vignesh
2016-01-11 4:50 ` Marek Vasut
2016-01-11 4:50 ` Marek Vasut
2016-01-12 4:59 ` Vignesh R
2016-01-12 4:59 ` Vignesh R
2016-01-12 13:50 ` Marek Vasut
2016-01-12 13:50 ` Marek Vasut
2015-08-27 17:44 ` [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver vikas
2015-08-27 17:44 ` vikas
2015-08-27 18:12 ` Marek Vasut
2015-08-27 18:12 ` Marek Vasut
2015-08-27 20:18 ` vikas
2015-08-27 20:18 ` vikas
-- strict thread matches above, loose matches on Subject: below --
2014-12-05 19:35 [PATCH 0/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Graham Moore
2014-12-05 19:35 ` [PATCH 2/2] " Graham Moore
2014-12-05 19:35 ` Graham Moore
2014-12-05 22:30 ` Rafał Miłecki
2014-12-05 22:30 ` Rafał Miłecki
2014-12-08 16:54 ` Graham Moore
2014-12-08 16:54 ` Graham Moore
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=20150826180631.GS81844@google.com \
--to=computersforpeace@gmail.com \
--cc=atull@opensource.altera.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=dwmw2@infradead.org \
--cc=grmoore@opensource.altera.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=vikas.manocha@st.com \
--cc=yvanderv@opensource.altera.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.