On Fri, Oct 19, 2018 at 09:22:08AM +0200, Geert Uytterhoeven wrote:
> Hi Christoph,
>
> On Fri, Oct 19, 2018 at 9:10 AM Christoph Hellwig wrote:
> > On Fri, Oct 19, 2018 at 09:07:51AM +0200, Geert Uytterhoeven wrote:
> > > Without this:
> > > - It's hard to visually match your untagged cover
Hi Christoph,
On Fri, Oct 19, 2018 at 9:10 AM Christoph Hellwig wrote:
> On Fri, Oct 19, 2018 at 09:07:51AM +0200, Geert Uytterhoeven wrote:
> > Without this:
> > - It's hard to visually match your untagged cover letter with the
> > actual patches,
> > - Your individual patches lack the
On Fri, Oct 19, 2018 at 09:07:51AM +0200, Geert Uytterhoeven wrote:
> Without this:
> - It's hard to visually match your untagged cover letter with the
> actual patches,
> - Your individual patches lack the version info, so people cannot see which
> version review comments in an email
Hi Christoph,
On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig wrote:
> On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote:
> > Please use "git format-patch -v --cover" to prepare patch series
> > for sending with git-send-email.
> >
> > "-v" to prefix all patches with version
On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote:
> Please use "git format-patch -v --cover" to prepare patch series
> for sending with git-send-email.
>
> "-v" to prefix all patches with version number ,
> "--cover" to have a "[PATCH 0/]" prefix in the cover letter.
We had
Hi Christoph,
On Wed, Oct 17, 2018 at 10:03 AM Christoph Hellwig wrote:
> currently every architecture that wants to provide on of the common
> periphal busses needs to add some boilerplate code and include the
> right Kconfig files. This series instead just selects the presence
> (when
