Greg Kroah-Hartman writes:
> + * sysfs_create_groups - given a directory kobject, create a bunch of
> attribute groups
> + * @kobj:The kobject to create the group on
> + * @groups: The attribute groups to create, NULL terminated
> + *
> + * This function creates a bunch of attribute
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
+ * sysfs_create_groups - given a directory kobject, create a bunch of
attribute groups
+ * @kobj:The kobject to create the group on
+ * @groups: The attribute groups to create, NULL terminated
+ *
+ * This function creates a bunch
uld configure perf to
use that location without pulling in the sanitized headers.
Sorry if anyone wasted their time chasing down my carelessness.
(Although, to be fair, 'perf' is the only package out of about 20 that
fails when I explicitly point the build at the target's "include"
directory.)
T
without pulling in the sanitized headers.
Sorry if anyone wasted their time chasing down my carelessness.
(Although, to be fair, 'perf' is the only package out of about 20 that
fails when I explicitly point the build at the target's include
directory.)
Thanks again!
Best regards,
Anthony Foiani
(
cd tools/perf
make O="$build" ARCH="$arch" CROSS_COMPILE="$TARGET_TUPLE"- V=1 \
EXTRA_CFLAGS="-I $PLATFORM_STAGE/include -I
$PLATFORM_STAGE/include/elfutils" \
LDFLAGS="-L$PLATFORM_STAGE/lib -lz -lb
/include -I
$PLATFORM_STAGE/include/elfutils \
LDFLAGS=-L$PLATFORM_STAGE/lib -lz -lbz2 \
DESTDIR=$PLATFORM_STAGE \
install || exit $?
)
Again, this all worked fine for 3.4.
Is there an obvious fix for 3.9?
Many thanks in advance.
Best regards,
Anthony
Greg KH writes:
> Is this really needed? For the large majority of the stable
> patches, specifically enumerating this isn't a big deal, it's a tiny
> patch, and if you think I'll remember to tell you which specific
> clause you didn't follow, then you think I have more spare time than
> I
Greg --
Thanks for the very quick response.
Greg KH writes:
> This is an obvious one, it needs to be upstream first.
>
> Or if not, a whole lot of explaination saying that you know it
> isn't, and why it isn't, and why it isn't applicable there,
I thought that I did provide exactly this
From: Anthony Foiani
Having recently received a formletter rejection on a stable patch, I
found it difficult to determine exactly which guideline I had missed.
Numbering the guidelines will allow the stable maintainer to quickly
and easily indicate which guidelines have not been followed
Greg KH writes:
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
My checklist against stable_kernel_rules.txt is below.
I could only find two reasons why you are saying
Greg KH g...@kroah.com writes:
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
My checklist against stable_kernel_rules.txt is below.
I could only find two reasons why you
From: Anthony Foiani anthony.foi...@gmail.com
Having recently received a formletter rejection on a stable patch, I
found it difficult to determine exactly which guideline I had missed.
Numbering the guidelines will allow the stable maintainer to quickly
and easily indicate which guidelines have
Greg --
Thanks for the very quick response.
Greg KH g...@kroah.com writes:
This is an obvious one, it needs to be upstream first.
Or if not, a whole lot of explaination saying that you know it
isn't, and why it isn't, and why it isn't applicable there,
I thought that I did provide exactly
Greg KH gre...@linuxfoundation.org writes:
Is this really needed? For the large majority of the stable
patches, specifically enumerating this isn't a big deal, it's a tiny
patch, and if you think I'll remember to tell you which specific
clause you didn't follow, then you think I have more
s
replacement to see if it has the same issue.
Signed-Off-By: Anthony Foiani
---
drivers/mtd/mtdcore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/mtdcore.c b/drivers/mtd/mtdcore.c
index c510aff..ac624df 100644
--- a/drivers/mtd/mtdcore.c
+++ b/drivers/mtd/mtdcor
if it has the same issue.
Signed-Off-By: Anthony Foiani anthony.foi...@gmail.com
---
drivers/mtd/mtdcore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/mtdcore.c b/drivers/mtd/mtdcore.c
index c510aff..ac624df 100644
--- a/drivers/mtd/mtdcore.c
+++ b/drivers/mtd
16 matches
Mail list logo
