From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp"
<Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp>
Cc: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
"'Valdis Kletnieks'" <valdis.kletnieks@vt.edu>,
"Motai.Hirotaka@aj.MitsubishiElectric.co.jp"
<Motai.Hirotaka@aj.MitsubishiElectric.co.jp>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Mori.Takahiro@ab.MitsubishiElectric.co.jp"
<Mori.Takahiro@ab.MitsubishiElectric.co.jp>,
"'linux-fsdevel@vger.kernel.org'" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] staging: exfat: remove fs_func struct.
Date: Thu, 23 Jan 2020 09:52:05 +0300 [thread overview]
Message-ID: <20200123065205.GH1847@kadam> (raw)
In-Reply-To: <OSAPR01MB1569F24512678DEA1C175504900F0@OSAPR01MB1569.jpnprd01.prod.outlook.com>
On Thu, Jan 23, 2020 at 06:38:53AM +0000, Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp wrote:
> Hello, Greg.
>
> Thank you for the quick reply.
>
> > Also the patch does not apply to the linux-next tree at all, so I can't take it.
> The patch I sent was based on the master branch of “https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/”
> and its tag was v5.5-rc6.
>
> > Also the patch does not apply to the linux-next tree at all, so I can't take it. Please rebase and resend.
> I will send a new patch based on the latest master branch of “https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git”.
>
>
> By the way, could you answer below questions for my sending patches in future?
> 1. Which repository and branch should be based when creating a new patch?
> 2. How do I inform you about a base on which I create a patch?
Always base it on staging-next or linux-next.
No need to inform us. If it doesn't apply Greg will email you.
regards,
dan carpenter
next prev parent reply other threads:[~2020-01-23 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 6:20 [PATCH] staging: exfat: remove fs_func struct T.Kohada
2020-01-22 8:57 ` Greg Kroah-Hartman
2020-01-23 6:38 ` Kohada.Tetsuhiro
2020-01-23 6:52 ` Dan Carpenter [this message]
2020-01-23 7:04 ` me
2020-01-23 7:25 ` Dan Carpenter
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=20200123065205.GH1847@kadam \
--to=dan.carpenter@oracle.com \
--cc=Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp \
--cc=Mori.Takahiro@ab.MitsubishiElectric.co.jp \
--cc=Motai.Hirotaka@aj.MitsubishiElectric.co.jp \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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.