The pull request you sent on Fri, 26 Feb 2021 01:42:04 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6fbd6cf85a3be127454a1ad58525a3adcf8612ab
Thank you!
--
Deet-d
The pull request you sent on Mon, 10 Aug 2020 01:44:22 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.9
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/fc80c51fd4b23ec007e88d4c688f2cac1b8648e7
Thank you!
--
Deet-do
The pull request you sent on Sun, 15 Sep 2019 22:27:05 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d7b0827f28ab3a4fd65864451ffefa695e3255fd
Thank you!
--
Deet-do
On Thu, Sep 19, 2019 at 8:48 PM Linus Torvalds
wrote:
>
> No problem. I'm used to merges, and I appreciate the heads-up.
Heh. The Kbuild merge turns out to be painful for other trees too. I
suspect the module tree isn't going to be any worse than the
DEBUG_INFO_BTF conflict.
Linus
Hi Linus,
On Wed, Sep 18, 2019 at 3:48 AM Jessica Yu wrote:
>
> +++ Will Deacon [17/09/19 19:16 +0100]:
> >Hi Jessica,
> >
> >On Tue, Sep 17, 2019 at 08:01:36PM +0200, Jessica Yu wrote:
> >> Yikes, I did not catch Stephen Rothwell's email about pausing the
> >> linux-next releases from Sept 5 unt
+++ Will Deacon [17/09/19 19:16 +0100]:
Hi Jessica,
On Tue, Sep 17, 2019 at 08:01:36PM +0200, Jessica Yu wrote:
Yikes, I did not catch Stephen Rothwell's email about pausing the
linux-next releases from Sept 5 until Sept 30
(https://lore.kernel.org/linux-next/20190904233443.3f73c...@canb.auug.o
Hi Jessica,
On Tue, Sep 17, 2019 at 08:01:36PM +0200, Jessica Yu wrote:
> Yikes, I did not catch Stephen Rothwell's email about pausing the
> linux-next releases from Sept 5 until Sept 30
> (https://lore.kernel.org/linux-next/20190904233443.3f73c...@canb.auug.org.au/).
>
> The modules-next namesp
+++ Masahiro Yamada [18/09/19 02:26 +0900]:
Hi Jessica, Linus,
On Wed, Sep 18, 2019 at 12:09 AM Jessica Yu wrote:
+++ Masahiro Yamada [15/09/19 22:27 +0900]:
>Hi Linus,
>
>This is a Kbuild pull request for v5.4-rc1.
>I am sending this a bit earlier.
>Please pull it in when you open the merge
Hi Jessica, Linus,
On Wed, Sep 18, 2019 at 12:09 AM Jessica Yu wrote:
>
> +++ Masahiro Yamada [15/09/19 22:27 +0900]:
> >Hi Linus,
> >
> >This is a Kbuild pull request for v5.4-rc1.
> >I am sending this a bit earlier.
> >Please pull it in when you open the merge window.
> >
> >Thanks.
>
> Hi Masa
+++ Masahiro Yamada [15/09/19 22:27 +0900]:
Hi Linus,
This is a Kbuild pull request for v5.4-rc1.
I am sending this a bit earlier.
Please pull it in when you open the merge window.
Thanks.
Hi Masahiro, Linus,
There is a merge conflict between the kbuild and modules-next tree.
Specifically,
The pull request you sent on Wed, 8 May 2019 23:47:39 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2646719a48c21ba0cae82a3f57382a9573fd8400
Thank you!
--
Deet-doo
The pull request you sent on Sat, 9 Mar 2019 10:31:35 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ffd602eb4693bbb49b301fa059b109bbdebf9524
Thank you!
--
Deet-doo
On Sun, Oct 28, 2018 at 10:12 AM Masahiro Yamada
wrote:
>
> Please pull Kbuild updates for v4.20
Pulled,
Linus
Hi Linus,
2018-06-14 15:26 GMT+09:00 Linus Torvalds :
> On Thu, Jun 14, 2018 at 3:16 AM Masahiro Yamada
> wrote:
>>
>> Could you run sed directly in your tree?
>
> Sure, I did that on the plane. Now on the ground, pushed out.
> Somebody should double- and triple-check it.
>
I double-checked it
On Thu, Jun 14, 2018 at 3:16 AM Masahiro Yamada
wrote:
>
> Could you run sed directly in your tree?
Sure, I did that on the plane. Now on the ground, pushed out.
Somebody should double- and triple-check it.
Linus
Hi Linus,
2018-06-14 2:49 GMT+09:00 Linus Torvalds :
> On Wed, Jun 13, 2018 at 10:29 AM Masahiro Yamada
> wrote:
>>
>> I cannot come up with a name better than CC_STACKPROTECTOR_STRONG.
>
> How about just calling it STACKPROTETOR_STRONG and leaving it at that?
Good idea!
> Make the "CC_HAVE_xyz
On Wed, Jun 13, 2018 at 10:29 AM Masahiro Yamada
wrote:
>
> I cannot come up with a name better than CC_STACKPROTECTOR_STRONG.
How about just calling it STACKPROTETOR_STRONG and leaving it at that?
Make the "CC_HAVE_xyz" model for compiler feature tests, but when
actually picking an actual optio
Hi Linus,
2018-06-14 1:03 GMT+09:00 Linus Torvalds :
> On Wed, Jun 13, 2018 at 8:55 AM Linus Torvalds
> wrote:
>>
>> On Wed, Jun 13, 2018 at 7:47 AM Masahiro Yamada
>> wrote:
>> >
>> > Please pull more Kbuild updates.
>>
>> Pulled. However, I notice a few oddities.
>
> Oh, and one actual bug: "m
On Wed, Jun 13, 2018 at 9:03 AM Linus Torvalds
wrote:
>
> This is a pretty dangerous silent change.
I've merged it despite this, but I think we need to revisit the whole
issue. Possibly by just renaming that option, so that people _see_ the
change and get asked about it.
Linus
On Wed, Jun 13, 2018 at 8:55 AM Linus Torvalds
wrote:
>
> On Wed, Jun 13, 2018 at 7:47 AM Masahiro Yamada
> wrote:
> >
> > Please pull more Kbuild updates.
>
> Pulled. However, I notice a few oddities.
Oh, and one actual bug: "make oldconfig" doesn't work right.
I used to have
CONFIG_HAVE_CC
On Wed, Jun 13, 2018 at 7:47 AM Masahiro Yamada
wrote:
>
> Please pull more Kbuild updates.
Pulled. However, I notice a few oddities.
This causes a non-clang build to have
CLANG_VERSION=0
in the config file. Maybe that's intentional to simplify other
expressions (ie allow "depends on CLANG
Hi Yamada-san,
On Mon, Nov 27, 2017 at 1:17 PM, Masahiro Yamada
wrote:
> 2017-11-27 17:30 GMT+09:00 Geert Uytterhoeven :
>> On Fri, Nov 24, 2017 at 5:58 PM, Masahiro Yamada
>> wrote:
>>> Please pull a little more Kbuild updates for v4.15.
>>> The reason for lateness is I hesitated to put some pa
Hi Geert,
2017-11-27 17:30 GMT+09:00 Geert Uytterhoeven :
> Hi Chris, Yamada-san,
>
> On Fri, Nov 24, 2017 at 5:58 PM, Masahiro Yamada
> wrote:
>> Please pull a little more Kbuild updates for v4.15.
>> The reason for lateness is I hesitated to put some patches
>> in the last week pull requests du
Hi Chris, Yamada-san,
On Fri, Nov 24, 2017 at 5:58 PM, Masahiro Yamada
wrote:
> Please pull a little more Kbuild updates for v4.15.
> The reason for lateness is I hesitated to put some patches
> in the last week pull requests due to big conflicts.
> Also, I applied some fixes and trivial enough o
On Fri, May 27, 2016 at 01:20:29PM -0700, Linus Torvalds wrote:
> I didn't look at the details of your patch, but I did look at several
> IS_ERR_VALUE() uses in the standard kernel, and they were basically
> all wrong. Even the ones that used it for the rigth reason (vm_brk()
> that returns a poin
On Friday, May 27, 2016 1:20:29 PM CEST Linus Torvalds wrote:
> On Fri, May 27, 2016 at 1:04 PM, Arnd Bergmann wrote:
> >
> > In fact, the patch that I have in my private tree that was hiding the
> > warning for me on x86 is one that removes all instances of IS_ERR_VALUE()
> > with arguments other
On Fri, May 27, 2016 at 1:04 PM, Arnd Bergmann wrote:
>
> In fact, the patch that I have in my private tree that was hiding the
> warning for me on x86 is one that removes all instances of IS_ERR_VALUE()
> with arguments other than 'unsigned long', see http://pastebin.com/uYa2mkgC
> for reference.
On Friday, May 27, 2016 10:23:00 AM CEST Linus Torvalds wrote:
> On Fri, May 27, 2016 at 5:33 AM, Arnd Bergmann wrote:
> >
> >
> > gcc can not always figure out which code is only used in an error
> > condition an assignment to indirect argument is only done after the
> > use of IS_ERR() catches e
On Fri, May 27, 2016 at 10:23 AM, Linus Torvalds
wrote:
>
> This code:
>
> if (IS_ERR(hash))
> return PTR_ERR(hash);
>
> is obviously "return non-zero" to a kernel developer (because that's
> how our error codes work), but to a compiler that "return PTR_ERR()"
> ends up cas
On Fri, May 27, 2016 at 5:33 AM, Arnd Bergmann wrote:
>
>
> gcc can not always figure out which code is only used in an error
> condition an assignment to indirect argument is only done after the
> use of IS_ERR() catches errors. In gfs2, this results in a warning
> about correct code:
I figured
On Thursday, May 26, 2016 10:26:50 PM CEST Linus Torvalds wrote:
> On Thu, May 26, 2016 at 1:33 PM, Michal Marek wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kbuild
>
> This pull results in new warnings.
>
> I get new "may be uninitialized" warnings now for me
On Thu, May 26, 2016 at 1:33 PM, Michal Marek wrote:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kbuild
This pull results in new warnings.
I get new "may be uninitialized" warnings now for me allmodconfig
build, and while I didn't look at them all, the one I looked at w
On Thu, Oct 11, 2007 at 07:08:53PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 10 Oct 2007, Sam Ravnborg wrote:
> >
> > This set of commits are the kbuild stuff that does not
> > conflict with the pending x86 merge.
>
> Hmm. It does for me, actually.
I did not try it out obviously - I just remov
On Wed, 10 Oct 2007, Sam Ravnborg wrote:
>
> This set of commits are the kbuild stuff that does not
> conflict with the pending x86 merge.
Hmm. It does for me, actually.
I fixed up the trivial conflict in the main Makefile, but that seems to
leave $(ARCH) entirely undefined in my case, so the
34 matches
Mail list logo
