From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Geert Uytterhoeven
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>,
Pantelis Antoniou
<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] configfs: Remove ppos increment in configfs_write_bin_file
Date: Thu, 30 Jun 2016 16:19:48 +0200 [thread overview]
Message-ID: <20160630141948.GA19378@lst.de> (raw)
In-Reply-To: <577515C6.5050802-ynQEQJNshbs@public.gmane.org>
On Thu, Jun 30, 2016 at 02:51:18PM +0200, Marek Vasut wrote:
> > sorry for the delay. I've applied the fix and will send it out to
> > Linus for the 4.7 merge window.
>
> No problem, glad to see it applied, thanks!
>
> btw. is this (devicetree@) the correct list for such a patch or should
> this be sent to some other list (linux-fsdevel@ maybe) ?
I don't think devicetree is anywhere near right. fsdevel and lkml
are the right place.
--
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:[~2016-06-30 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 14:16 [PATCH] configfs: Remove ppos increment in configfs_write_bin_file Marek Vasut
[not found] ` <1463581011-9910-1-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2016-06-28 16:30 ` Marek Vasut
[not found] ` <5772A624.6040801-ynQEQJNshbs@public.gmane.org>
2016-06-30 9:26 ` Christoph Hellwig
[not found] ` <20160630092616.GA9099-jcswGhMUV9g@public.gmane.org>
2016-06-30 12:51 ` Marek Vasut
[not found] ` <577515C6.5050802-ynQEQJNshbs@public.gmane.org>
2016-06-30 14:19 ` Christoph Hellwig [this message]
[not found] ` <20160630141948.GA19378-jcswGhMUV9g@public.gmane.org>
2016-06-30 14:35 ` Marek Vasut
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=20160630141948.GA19378@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
--cc=marex-ynQEQJNshbs@public.gmane.org \
--cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@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).